http://bugzilla.moblin.org/show_bug.cgi?id=5188
--- Comment #11 from Chen Congwu <[email protected]> 2009-09-17 01:59:23 --- (In reply to comment #10) > (In reply to comment #9) > How do you solve this at the moment with outgoing OBEX? Where does the > connection information come from? I was using agent->setSyncURL after agent is created. > To some extend, extending createTransport() > will be inevitable. Otherwise the client won't know whether it should create > > an HTTP or an OBEX transport. Right. > For us that means that "disconnect()" can be a long-running operation (last > message might still get transmitted) that we may want to abort. I therefore > suggest the following API change for TransportAgent: > Agree -- 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. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
