JHildebrand at jabber.com
Fri Jan 16 16:13:18 UTC 2004
Please take a look at JEP 124, and see if there is anything you would like
added to that. JEP 25 was informational, and I think the hope is that JEP
124 will be the standards-track replacement that will incorporate all of the
lessons learned about HTTP polling.
> -----Original Message-----
> From: SEN [mailto:sendel2000 at hotbox.ru]
> Sent: Tuesday, December 16, 2003 1:51 AM
> To: standards-jig at jabber.org
> Subject: [standards-jig] JEP-0025
> Please add to jep-0025 this things
> When Server recieve message from Client, it view HTTP Header
> and get "CookieID" from there, if "CookieID" not found it get
> it from message body (from field /identifier/) and with Key &
> NewKey Must work also with HTTP Header.
> It very usefull for programs poructs!
> Summary: Server based on jep-0025 must support two kind of request,
> 1. with HTTP Header:
> POST /wc12/webclient HTTP/1.1
> Content-Type: application/x-www-form-urlencoded
> CookieID: identifier
> [Key: key]
> [NewKey: new_key]
> Host: webim.jabber.com
> 2. original if 1 isnt successful (as in jep-0025 now)
> identifier ; key [ ; new_key] , [xml_body]
> Its simplest for parsing..
> and key must be optional...!!!!
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards