PHWinfo - Afficher un message

06/09/2006, 06h21

On Wed, 6 Sep 2006, Pete Maclean wrote:
>>> This should do it:
>>> 123 SEARCH UID 456
>> Better is
>> tag UID FETCH 456 UID
>> (or any other fetch item for the second UID).
> Mark, Why do you think the FETCH is better?

The FETCH result definitely associates the UID with the sequence number.
With SEARCH, the application has to do so manually.

The FETCH can be pipelined with other fetches.
The SEARCH can not be (not safely, anyway).

> I chose SEARCH because it's cleaner in the sense that, if the
> message with the given UID does not exist, the client does not have to deal
> with a NO response.

What makes you think that you would get a NO response? Any server that
returns a NO response in this case is broken.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

06/09/2006, 06h21	#5
Mark Crispin Messages: n/a Hébergeur:	Re: getting sequence number from UID On Wed, 6 Sep 2006, Pete Maclean wrote: >>> This should do it: >>> 123 SEARCH UID 456 >> Better is >> tag UID FETCH 456 UID >> (or any other fetch item for the second UID). > Mark, Why do you think the FETCH is better? The FETCH result definitely associates the UID with the sequence number. With SEARCH, the application has to do so manually. The FETCH can be pipelined with other fetches. The SEARCH can not be (not safely, anyway). > I chose SEARCH because it's cleaner in the sense that, if the > message with the given UID does not exist, the client does not have to deal > with a NO response. What makes you think that you would get a NO response? Any server that returns a NO response in this case is broken. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote.