Talk:OBject EXchange

From Wikipedia, the free encyclopedia
Jump to: navigation, search

So how can one connect SyncML (eg. jsync4) and (Open)OBEX?

As far as I know, SyncML runs over HTTP. OBEX runs over Bluetooth, IR, serial or USB cable.
A lot of the links on the buttom of the page seem like spam links, and should be removed. --Voidvector 19:51, 27 August 2006 (UTC)

How to add in the disambiguition that obex is also an anatomic part of the brain?

  • So really OBEX is nothing like HTTP? It's another protocol altogether. —Preceding unsigned comment added by 84.9.146.69 (talk) 23:58, 4 September 2007 (UTC)
I don't see why it's being compared to HTTP. It's not stateless, it's not binary. How is it similar? kasajian

Since OPP / Object Push Profile is redirected here, shouldn't we mention it in the article? kasajian —Preceding comment was added at 16:50, 4 May 2008 (UTC)

HTTP keep-alive[edit]

From the article:

HTTP transactions are inherently stateless; generally a HTTP client opens a connection, makes a single request, receives its response, and closes the connection. In OBEX, a single transport connection may bear many related operations.

I thought HTTP had keep-alive for this. How does OBEX keep-alive go beyond that of HTTP? --Damian Yerrick (talk | stalk) 23:01, 31 May 2008 (UTC)

HTTP keep-alive is used to avoid excessive open/close connection for a given server but does not guarantee that a single open-close will represent all request/response in a session. HTTP is based on the request-response pattern and includes no defined way of tying these to a single session. Cookies or URL query parameters are generally used for that in modern session-base web applications. —Preceding unsigned comment added by 24.16.147.215 (talk) 19:07, 6 October 2009 (UTC)