> > You mean to RFcomm channels do not behave the same as TCP ports where > multiple > clients can connect? > Exactly, RFcomm are point to point only. Even though that technically you could intercept the electromagnetic wave and see that information "illegally" obviously > But that should only matter on the receiving side, sending to multiple > clients > (unicast) should work just fine. > Yes that's right, but in that case you have multiple RFcomm connections, and each connection has it's own port. Normally you don't care about this, and let the Bluetooth Stack decide for you (BlueZ in this case)
> A multicast/broadcast wouldn't work work anyway, as OBEX cannot work > connectionless. > That was what I thought, but I wasn't sure. Cheers, Manuel ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
