From: Hendrik S. <po...@he...> - 2007-05-22 19:48:50
|
Am Dienstag 22 Mai 2007 21:23 schrieb Manuel Naranjo: > > So, Obex basically doesn't support 1 : N connections for one BT local > > device? > > I'm not sure if it's obex the one that doesn't support that. I'm sure > that Obex over BT will not support it. It doesn't mean you can't service > 1:N devices at the same time from the same bt local device, it means > that you can't use the same port for each of the N connections. What you > will have is N 1:1 connections, and not 1 1:N connection. > > > What happens if one client wants to connect to a server that is servicing > > the other client and only one BT local device is available? > > Never tried this, but I guess it will fail. If two devices want to > connect to the same RfComm port at the same time, only one will be able > to reach the port. But if your server is running in linux, and you have > BlueZ and OpenObex you actually can register/open more than 1 port, and > then you will not have this problem. What I'm not sure is if stupids > clients (phones for example) will be able to distinguish between one > port and the other and choose the one that's free, I'm sure that the > PalmOS is so stupid that doesn't. You mean to RFcomm channels do not behave the same as TCP ports where multiple clients can connect? But that should only matter on the receiving side, sending to multiple clients (unicast) should work just fine. A multicast/broadcast wouldn't work work anyway, as OBEX cannot work connectionless. HS |