Re: [Agendaware-dev-client] XML APIs
Status: Inactive
Brought to you by:
zacklink
|
From: zack <za...@th...> - 2002-02-07 02:36:48
|
Just read the server update. Moving right along, very cool. On the last_check_time mentioned below, I think we do need it for 2 reasons... 1) If the user moves from 1 box to another, the user would only get messages not downloaded on their other machine. POP3 has similar issues. With last_time_check, it will be much easier for the client to check the local db and sync just what it needs. 2) In case of the client detecting some internal inconsistency, it will have more power itself to recover from data integrity problems, while still minimizing bandwidth, responsiveness and server load. The client should be able to get up to speed on the comms pretty quickly, in fact, if no one else is working on it, I will do some work on that soon. Thanks, Zack Shane Turner wrote: > Just some thoughts regarding APIS. I've run into a few areas where it > seems the APIs don't make much sense so I wanted to get some feedback. > The main one I wanted to ask about was the RetrieveMailRequest. > It currently looks like this. > > <RetrieveMailRequest mailbox="xxx" request_id="xxx" format="header" > last_check_time="xxx"/> > > Where last_check_time is used to indicate a timestamp of the last time > the client checked for messages. I was thinking that the server ought > to be able to know what new messages have been delivered but haven't been > requested by the client so I was wondering if maybe we should change > last_check_time to something like "type" where the applicable values > would be "all" meaning to retrieve all messages and "new" meaning to only > give back new messages. last_check_time just doesn't seem appropriate. > > What do you guys think? > > Next, I was looking at the client code and it doesn't look like we're in > sync with the APIs with respect to responses and such. Just as a helper, > when I get the next version of the server out, I'm going to send small > command line programs that can be used to connect to the server and view > the different responses. I'll also include the exact APIs that the server > understands then you guys can let me know if there's things I need to > change or if you agree with the state of the APIs. > > Any problems or questions? > > > > __________________________________________________ > Do You Yahoo!? > Send FREE Valentine eCards with Yahoo! Greetings! > http://greetings.yahoo.com > > _______________________________________________ > Agendaware-dev-client mailing list > Age...@li... > https://lists.sourceforge.net/lists/listinfo/agendaware-dev-client > > > |