[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] [lwip] IOCTL
From: |
Recker, John |
Subject: |
[lwip-users] [lwip] IOCTL |
Date: |
Wed, 08 Jan 2003 22:10:07 -0000 |
I've been looking at lwip with the idea of using it
to run tcp/ip across a bluetooth connection. Seems pretty
doable, but there are BT features that aren't easily
exposed through the standard socket style interface.
(The primary issue is that Bluetooth doesn't expose
a "party-line" interface like a ethernet wire. Instead,
a bunch of work must be done to establish a connection
prior to issueing the first network packet).
So it seems like adding a ioctlsocket call would a reasonable
compromise.
I would like to guarantee order of execution (eg previously
issued API calls execute prior to calling my ioctl). Is there
a way to do this, or would I be best off creating a new message
type and using api_msg_post?
Any suggestions are appreciated...
thanx,
jr
[This message was sent through the lwip discussion list.]
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-users] [lwip] IOCTL,
Recker, John <=