Mike Robins(deleted)
|
Application interface to io-pkt for TCP and QNET
|
Mike Robins(deleted)
12/17/2010 2:29 AM
post79119
|
Application interface to io-pkt for TCP and QNET
I am porting an application to QNX (I'm relatively new to QNX) that utilizes
TCP/IP sockets to implement client-server IPC. I want to maintain the ability
to use TCP/IP because my test server only runs on Windows.
I would like my application to utilise native communications when client and
server are both running on QNX. My reading seems to indicate that io-pkt can
utilise TCP or QNET so I would like to have my application talk to the io-pkt
and open a connection across either protocol. I'll know which protocol would
be needed at run time so can give suitably different addresses or what ever.
I want the application to treat the connection as a socket regardless of
the transport mechanism. That is, I want a socket interface implemented
across a channel rather than IP. Isn't this what io-pkt does?
I don't want to have to re-implement the server as a resource manager.
I can't find straight forward examples of using io-pkt.
Have I got the wrong end of the stick? Is the situation that io-pkt either
resource manages the /dev/socket OR /dev/net namespace and the two are accessed
differently: TCP/IP through libsocket and QNET through libc?
In which case is io-pkt smart enough to notice that I am opening a local
TCP socket and implement it really efficiently?
Any help would be appreciated.
PS my application uses the Boost::asio library
|
|
|