[Syncevolution-issues] [Bug 5188] Outgoing obex connection for SyncEvolution
http://bugzilla.moblin.org/show_bug.cgi?id=5188
--- Comment #3 from Chen Congwu <congwu.chen(a)intel.com> 2009-09-14 00:39:24 ---
(In reply to comment #2)
> Change EvolutionSyncClient::createTransportAgent, now adds a
type parameter to
> indicate what type of transport will be created. Currently I am hard coding it
> to be OBEX_BLUETOOTH but should be dynamic later. I suggest add another
> property at the server configuration (Transport Type = xxx).
What about overloading the syncURL? We can use an HTTP transport for methods
http:// and https:// and then add our own pseudo-URLs for other methods, like
bluetooth://<MAC>:<channel> for outgoing OBEX via Bluetooth.
Adding the
transport parameter have another effect: a transport can have
multiple implementations, we can choose one at runtime. (like HTTP_CURL and
HTTP_SOUP, which we currently make the selection during compile time).
Another thing is I haven't found URL schemes like
"bluetooth://<MAC>:<channel>", looks a little awkward...
> Obex impelmentation discussions:
> 2. Small blocking operations
> After send before recv, use select to poll(non-blocking) but there are still
> small blocking operations (connect in ObexTransportConnect, send in
> OBEX_Request). Should be better removed later.
We need to integrate all long blocking IO with a GMainLoop. Can you do this?
Sure, I will improve this.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.