Hi Erich:
If you're trying to establish a connection to the TIPC topology server
(which uses port name {1,1}), you want to use tipc_send2name() rather
than tipc_connect2port().
The most basic approach is to send a zero length message, after which
the topology server will respond with a zero length message that
completes the connection handshaking (i.e. automatically calling
tipc_connect2port() for you). You can then use tipc_send() to send your
subscription requests to the topology server.
Alternatively, if you only need to send a single subscription, you can
send it when you do the initial tipc_send2name() call.
Regards,
Al
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Erich Focht
Sent: Friday, February 22, 2008 12:05 PM
To: [email protected]
Subject: [tipc-discussion] port name -> port_id ?
Hello,
with the native interface I'd like to do (inside a kernel module):
tipc_connect2port(myref, subscr_service);
I know the target port name {1, 1} but how can I get the port_id, which
is required as argument to tipc_connect2port? The function
tipc_nametbl_translate isn't exported...
Thanks,
Erich
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
