first important sub case is missing:Propably we need two top level protocols, one for 1-to-1 chat and one
for Conference chat.
we need to find a common ground.
Yup
now we come to the next use cases:
one to one
-> establish a session
-> ring partner
-> agree on a transmission approach with user
-> transmit data
-> leave a session
-> graceful session leave
-> shut down socket
Yup
multi partner conferences
-> find a session (through browsing server)
-> create a session
-> leave a session
-> mute a user [please, not that p2p discussion on recieving and sending
100 streams to/from multiple users]
-> kick a user
-> ban a user
-> etc. [see MUC use cases]
-> agree on transmission approach with session (whether server or some other stream host)
from my point of view, they overlap at least in in this specific case - transmission approach from communication partner (server/session relay in multi partner conference or other client in 1-2-1).
the second sub case missing:
-> join a session
'join session' in MMUC (multi media user conference) corresponds loose to establish a session in 1-2-1.
u
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
