[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CAP: why do we need GENERATEUID?





GENERATEUID is there for clients who have difficulty generating
properly unique IDs.  iCal recommends that UIDs be based on
hostname or IP address to assure their uniqueness.  This is a
problem in environments where hostnames can be rapidly
reassigned, (dial-up connections or wireless devices) or
environments where hosts do not have properly unique hostnames or
IP addresses (192.168.x.x or 10.x.x.x).

In addition, it may allow applications on small devices to reduce
their memory footprint.

In response to some of John's earlier points:

Using GENERATEUID doeesn't mean an additional round-trip for each
create, a client can request many UIDs at once and store them
locally for that session, or forever.

Sometimes a single event requires multiple VEVENTs to represent
it, in these cases the client needs to add the UID to indicate
the proper linkage between the VEVENTs.

Returning the UID is problematic in the case where multiple
components are created, since the returned UIDs need to be
correlated with the components which were sent.

Alex

>>>>>  "George" == George Babics <georgeb@xxxxxxxxxxx> writes:
   George> To: John Stracke <francis@xxxxxxxx>
   George> Subject: Re: CAP: why do we need GENERATEUID?
   George> Date: Thu, 23 Aug 2001 11:15:32 -0400

   George>   The only thing that searching the archives revealed
   George> was the it was suggested that GENERATEUID be used to generate unique
   George> calids.

   George>   But as you suggested in an other post in this thread,
   George> the create can return the UID for the component it created.  Also,
   George> when you create a calendar, the calid can be returned to the
   George> client. This will save calls to the CS.


   George> George


   George> John Stracke wrote:
   >>
   >> GENERATEUID asks the CS to generate one or more unique UIDs. What is this
   >> for? Why can't the client create its own UIDs, like any other CUA?  Why
   >> should we introduce extra round-trips, and extra work on the CS?
   >>
   >> If there's some strong reason the UID has to be generated by the CS, then
   >> it should still not be done in a separate command; CREATE should accept
   >> components without UIDs, and report back the UIDs they were assigned.
   >>
   >> -- /==============================================================\ |John
   >> Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist
   >> |=============================================| |eCal Corp.  |"Baldric,
   >> how did you manage to find a turnip| |francis@xxxxxxxx
   >> <mailto:francis@xxxxxxxx>|that cost 400,000 pounds?" "Well, I had to | |
   >> |haggle." --Blackadder III |
   >> \==============================================================/


--


--Paul Hoffman, Director
--Internet Mail Consortium