Subject: RE: [Simple] Requirements to SIMPLE components continuation

From: "Stephen Gryphon" <[email-masked]>
Date: Mon, 25 Mar 2002 10:44:40 +1100

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> - Private messages in a multiparty centralized conference 
> with messaging sessions. This means that if a number of 
> participants are in a conference/chat via a centralized 
> server it should be possible to send a private (i.e. only 
> shown to the selected recipient, not the whole conference) 
> message between two participants. It must be possible to 
> correlate it somehow on the ongoing conference, so that it 
> can be shown correctly on recipient's chat window, meaning 
> that a completely separate one-shot message is not the right solution.

The central conferencing model we are basing our work on is similar to a mailing list, where when a message is posted the Request-URI and the To field are both the conference/address, with the From address as the speaker. This is then delivered to the conference server.

The conference server then distributes the MESSAGE to all participants, setting the Request-URI to the correct value for each recipient (but keeping the To field as the conference name). [NB. It is not unusual for the To and Request-URI to not match, e.g. when proxying.]

We are also assuming that threading is based on the Call-ID (or the In-Reply-To) field.

This means that (a) A MESSAGE could be sent directly to the recipients address, or (b) A MESSAGE could be sent to the conference Request-URI, but with the To field as the indended individual recipient (this lets the conference server know to only forward to that participant).

In both cases the Call-ID should be set appropriately (this also lets the conference server know which conference the private message is part of). It is the Call-ID (or In-Reply-To) that determines the threading and should be used by the UI to display the message in context (as per the Components draft).

In short:
- The UI should correlate the conference based on the Call-ID.
- Separate one-shot should then be displayed correctly, if it can get through and passes all security checks.
- For a complete record the MESSAGE can still go via the conference server by using an appropriate Request-URI (and Call-ID), with the intended To field.

Hope this helps.

- Sly
_______________________________________________
simple mailing list
[email-masked]
http://mailman.dynamicsoft.com/mailman/listinfo/simple