Zitat von "Luiz Augusto von Dentz" <[email protected]>: > You mean OBEX_ResumeRequest take the response,
That's not what I meant. With OBEX_SuspendRequest(), you can choose the object to use, with OBEX_ResumeRequest(), it always is the current one. > that could work but of > course we will need to change the logic so that it doesn't always try > to resume the stream, taking the object sound good to me. But note > that OBEX_ObjectSetRsp is still needed when request are not suspended, > so if I were to deprecated anything it would be No, I meant to replace OBEX_ObjectSetRsp(object, rsp, lastrsp) with OBEX_SetResponse(self, object-or-NULL, rsp, lastrsp) so it matches the use-cases of SuspendRequest and ResumeRequest. BTW: There is no need for a new obex_object for a server, use the present one in your patch. And then suddently, it is the same as an OBEX_SetResponse() (the actual sending is done in OBEX_ResumeRequest()). > OBEX_ResumeRequest/OBEX_SuspendRequest/OBEX_CancelRequest making > openobex to never respond/request automatically to requests/responses, > or if this is too much to start with we can just make some API change > so the user application can request to operate on asynchronous > (MainLoop based) or synchronous (thread based) mode. I kind of like the automatic "sending responses" behind the scenes... HS ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
