On Sun, 2004-08-01 at 10:39, Phil Dibowitz wrote: > Phil Dibowitz wrote: > > Unfortunately the DCU-11 cable that connects the phone is a USB to > > Serial converter, and the phone acts as a basic serial device taking AT > > commands. > > > > Therefore multisync writes some data, and then tries a few times to > > write more data but fails and therefore gives up. > > I managed to "work around" this by adding a "sleep" in obex_cable_write. > > I was uber-conservative the first time and did a sleep(30) just before > the close of the while() loop. This obviously took a very long time > (sleep for 30 seconds after each write), but it WORKED! I've dropped it > down to 5 and am recompiling now. > > This is probably much less than an ideal solution, but hopefully it'll > help those more familiar with the codebase come up with a cleaner solution.
I am not familiar with the irmc plugin, but shouldnt that be writen with poll/select to check if it is possible to write to the socket? ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
