Marcel, > in the most cases this is a hardware port. It can be emulated, but > that is not the usual case. > Ouu ok. Not good for me then. > You can't really do that over D-Bus. Use the native RFCOMM sockets > from the Bluetooth library. > 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? Thanks, Manuel ------------------------------------------------------------------------- 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
