[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] BT apps: What about client code?
Knowing that 'experimental' apps are not so experimental is quite a good
Running apps/bluetooth/experimental/btdm as a server is quite functional
(exept crashes while closing the connection), but what about the client
code? (not implemented according to line 451 of btd.c).
(Thus I use the old btd (/apps/bluetooth/btd) to run as a client).
Does there is a way to use the 'experimental' code as a client with PPP?
Thanks a lot.
> -----Original Message-----
> From: Mattias Ågren [mailto:firstname.lastname@example.org]
> Sent: Tuesday, June 26, 2001 2:45 PM
> To: 'email@example.com'
> Subject: [bluetooth-dev] BT apps
> Hi All,
> I have seen some problems on this list due to that some
> people are using the 'old' btd (apps/bluetooth/btd/) instead
> of the 'new' (apps/bluetooth/experimental).
> To avoid troubles with non-updated code in the /apps/bluetooth/btd
> directory I recommend everybody that doesn't use the 'experimental'
> apps to do so (see apps/bluetooth/experimental/README.txt for
> The name 'experimental' is slightly misleading as it's nowadays
> the only applications that we use and support fully.
> The intent is to make the bt_xxx files into a library later on.
> The only exception is the apps/userstack/btduser which still uses
> the old btd.c (new btd still doesn't support running usermode stack
> over sockets and using pty:s for ppp) but this will also be changed
> as soon as there is time for it.
> Mattias Ågren,
> AXIS Communications AB
> To unsubscribe from this list: send the line "unsubscribe
> bluetooth-dev" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com