Subject: RE: [Simple] Choosing a mechanism for presence publication.

From: "James Undery" <[email-masked]>
Date: Thu, 4 Jul 2002 16:29:16 +0100

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]

> My main concern is that if the PUBLISH gets big enough 
> contents, the PUA has to POST the presence info to some HTTP 
> server and send a PUBLISH to the Presence Server with 
> content-indirection. The Presence Serve then has to GET using 
> HTTP. This is like going around in a circle. Why not just use 
> HTTP in the first place and avoid all this.
> 
> BIND to the presence server can help you discover where to 
> publish your presence info using HTTP.

I sortof agree with Hisham here, how I envisaged this working was The presentity using BIND to provide the "compositor" with the locations of PUAs. Depending on the URL the compositor would then fetch and aggregate the information from the PUAs using a sutable mechanism (e.g. SIP scheme use SUB/NOT, HTTP use GET). The "compositor" itself would just look like a regular PUA to subscribers (i.e. use SUB/NOT).