On 10 Jul 2003, Timo Sirainen wrote: >On Thu, 2003-07-10 at 11:07, Andreas Aardal Hanssen wrote: >> This is exactly my point. How is the server to decide wether there is a >> bug in the client, or if the search was made in good faith because the >> client was slightly out of sync. I for one would not like to keep client >> state in mind when receiving SEARCH requests. >I don't really see where the problem is. Both client and server have to >know what messages map to which sequences and they have to be fully >synced all the time. If client requests sequences which don't exist, or
No, they are not fully synced all the time. That's impossible. How can a client always be in sync? How can you prevent a client from searching for messages with msn 1000:1050 when the last thing it knew was that such messages existed? >it shouldn't know about yet, it's clearly an error. >How is keeping client state in mind with SEARCH any different than with >FETCH? If you FETCH message 1000:1050 and there are no messages there, then that is an error. If you search for messages with msn 1000:1050 and there are none, then the search result is empty. There is no _error_ in searching for message number 1000:1050 even if that doesn't match anything. Error <=> BAD. Andy -- Andreas Aardal Hanssen http://www.bincimap.org/
