Hi Marcel,
my idea was to have an embedded device automatically
connecting to a host
system providing rfcomm. This embedded device might go down
from time to
time but should normaly be streaming sensor data. To keep
things easy I
thougt it would be advantageous to avoid implementing an ip
streaming in
favour of rfcomm.
Thatfor on hostside I wrote a script to have 'rfcomm listen'
restarted
everytime it goes down due to hangup. The embedded device
should
{,re}connect to it whenever it starts up.
This is working quite well with a single connection. I'm not
planning to
have more than one but the script would be more elegante if
this were
possible.
But this also does mean that I have to offer to stop a
channel without
closing one of the others.
You don't think that this is a good idea, do you?
Respect to all taking part!
Regards,
gerhard
2 files attached:
rc_rfcomm - bash start/stopscript (replace the function
'boot_mesg',
'evaluate_retval' and 'echo_warning' with something
appropriate or get
their definitions here:
http://www.linuxfromscratc
h.org/blfs/downloads/6.2.0/blfs-bootscripts-20060910.tar.bz2
)
rfcomm_listen - bash daemon script called from rc_rfcomm.
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
|
