[gpodder-devel] my.gpodder episode sync design problem: "since" values
- From: koeglstefan at gmail.com (Stefan Kögl)
- Date: Sat, 2 Jul 2011 13:55:47 +0200
Hello,
First thanks to both of you for sharing your ideas!
>>> At Fri, 1 Jul 2011 15:35:52 +0300, Dov Feldstern wrote:
>>>> So, I think that the "timestamp" stored with actions is *not* the
>>>> value which should be used for purposes of comparing with "since"
>>>> values and syncing; rather, an "upload-timestamp" should be stored
>>>> server-side, which would serve for this purpose.
I totally agree with you that using the client's timestamp for two
different purposes is a design issue.
>> On Fri, Jul 1, 2011 at 16:29, Neal H. Walfield <neal at walfield.org> wrote:
>>> Why not use Lamport timestamps to do the ordering?
>>>
>>> ?http://en.wikipedia.org/wiki/Lamport_timestamps
I'm currently thinking about a solution that would include both
approaches. For each action two timestamps are stored, the current one
from the client and a server-timestamp that is used for
synchronization. The server-timestamps could be implemented as Lamport
timestamps to make it possible (in the future) to distribute
gpodder.net over multiple servers. Additionally when doing the switch
from the current system, the server-timestamps could be initialized
with the current UTC timestamp so that we don't break any clients.
What do you think about this solution?
On Fri, Jul 1, 2011 at 4:54 PM, Dov Feldstern <dovdevel at gmail.com> wrote:
> Thinking about this a bit more, I think that using server-based
> action-upload times would also solve / obviate the need for solving
> https://bugs.gpodder.org/show_bug.cgi?id=1366 .
That's true, actually. However I'd rather continue the discussion here
because it has now grown to a much broader topic than what's
originally discussed in the bug.
-- Stefan
Other related posts:
