Re: Bluetooth-dev Digest, Vol 2, Issue 85
Re: Bluetooth-dev Digest, Vol 2, Issue 85
- Subject: Re: Bluetooth-dev Digest, Vol 2, Issue 85
- From: Esa Karjalainen <email@hidden>
- Date: Mon, 14 Nov 2005 16:13:51 +0200
Ouch.
Thanks for the reply, but that's no good for me. I need to be
able to send and receive RFCOMM packets hand-built over L2CAP.
The ability to see the bytes directly is sort of the point,
here.
Is there any way to circumvent this issue?
Thanks,
- Esa
>
> Message: 2
> Date: Fri, 11 Nov 2005 08:45:59 -0800
> From: Marco Pontil <email@hidden>
> Subject: Re: Help! Sending RFCOMM packet over L2CAP fails.
> To: Esa Karjalainen <email@hidden>
> Cc: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> This happens because the Apple RFCOMM implementation matches
> on the L2CAP channel with PSM 3 much before yours, and then makes
> that L2CAP channel unavailable to anybody else (there can be only one
> client).
>
> I would recommend you to use the Apple OBEX implementation, aside
> of the fact that it would workaround this specific issue it will save
> you a
> lot of work, it has really easy to use apis, and has been extensively
> tested.
>
> Should you decide to use your own obex, just build the connection over
> the RFCOMM APIs instead than building your own RFCOMM stack.
>
> ... Marco
>
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden