Am Sonntag 13 Januar 2008 schrieb Hendrik Sattler: > Am Samstag 12 Januar 2008 schrieb Eric Lapuyade: > > Yes. Once the connection is established, both endpoints can send > > requests. So OBEX_MODE_SERVER / OBEX_MODE_CLIENT is not even related to > > who connects/accept the connection. > > Where in the OBEX specs is this stated? > > The obex spec actually says: > "OBEX follows a client/server request-response paradigm for the > conversation format. The terms client and server refer to the > originator/receiver of the OBEX connection[...]. Requests are issued by the > client (the party that initiates the OBEX connection). Once a request is > issued, the client waits for a response from the server before issuing > another request. The request/response pair is referred to as an operation." > > This paragraph is pretty simple and clear: An OBEX server is not allowed to > issue requests. It may be possible to violate the specs but why should the > library support that?
That said: Sure you can use OBEX_Request() if you server also wants to act as a client, but it has to use OBEX_Init() first to get another obex_t. HS ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
