Manuel, > Ok if it's not there why not creating it? I can do it I think. Is there > any convention on how to do this? Any API proposal? > > I would say it should be something like: > methods: > listenRFcomm > closeRFcomm > > signals: > RFcommConnected > RfcommDisconnected > > Does it make any sense at all? I would say that maybe not, but it might > be a good idea to have an rfcomm wrapper. Something that creates the > rfcomm port, makes the connection and then just returns the rfcomm > device. Ideas? >From our experience using RFCOMM ttys is not a good idea. The bluetooth rfcomm tty driver in the kernel is too unreliable in certain situations. We actually have to patch our device kernels in order to get it working somewhat correctly. The CreateProxy is still your best bet, or you can use bluetooth rfcomm sockets and do it yourself. Regards, -Denis ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Bluez-devel mailing list Bluez-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/bluez-devel
