> -----Original Message----- > From: Jerry Ipe Thomas Sent: Tuesday, January 28, 2003 4:23 AM
> One possible way to get over this reeeeally scary scenario is to > match the subsequent NOTIFYs using the To tag in the 2xx to the > SUBSCRIBE??? Is this the right thing to do? Man! Forking sucks! This IS a > problem with devices that do not have much in terms of processing > horsepower or memory ( Say 33 MIPS and 64KB of SRAM. Remember that a lot > of "other strange modules", which are obviously not mine, are running > within that 64KB. ) to maintain separate dialogs with all those stupid > notifiers! > I am pissed! I think, this is the point where PUBLISH comes in. You can read in draft-ietf-simple-publish-01: ...The focus of this specification is to provide a framework for the publication of event state from a user agent to an entity that is responsible for compositing this event state and distributing it to interested parties through the SIP events [1] framework. This specification fills a gap in the SIP events framework to allow for a client to push its event state to the state agent that acts on its behalf. Franz _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
