Feature Requests item #1425528, was opened at 2006-02-06 11:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507006&aid=1425528&group_id=64305
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Bluetooth / serial port. New project? Initial Comment: TCP/IP support is great but probably the reason why MultiSync isn't a greatly used program is because we have to establish TCP/IP. Phones will never have decent support with this approach. This is no due to technicalities but what happens OFF the computer screens. Phone companies will not be encouraging TCP/IP if they possibly can because they'd rather you spent 50p each time you want to sync your phone. This means that support by /dev/rfcomm & (in an ideal world) /proc/usb.../ is the beginning. However, MultiSync is TCP/IP based. There's surely a big need for Bluetooth sync support? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507006&aid=1425528&group_id=64305 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Multisync-devel mailing list Multisync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/multisync-devel
