Hi Felix:
Currently I know of no way to retrieve the destination port ID
associated with a returned message, but I don't see why this couldn't be
added to TIPC as an enhancement. We'd probably want to introduce a new
object type (TIPC_DESTPORT?), and define the conditions under which this
info would be returned as ancillary data.
These definitions will require a bit of thought and discussion. For
example, a named message could conceivably return a TIPC_DESTPORT
object, in addition to a TIPC_DESTNAME object, however this might not
always be the case (eg. a message is returned because the specified name
is not found in the TIPC name table). We'd also need to consider cases
where the name translation is done by the receiving node, and when
broadcast traffic is involved. Fortunately, once we've defined the
behavior we want, I think the actual implementation of this enhancement
would be pretty simple.
If you're interested in seeing this added to TIPC, let me know. I'd be
happy to help you work on the definitions and to inspect any patch you'd
like to submit for inclusion in TIPC.
Regards,
Al
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Nayman Felix-QA5535
Sent: Tuesday, June 26, 2007 7:21 PM
To: tipc-discussion@lists.sourceforge.net
Subject: [tipc-discussion] Returned messages and retrieving the
destinationport id
I was wondering if there's a way of retrieving the destination address
for a returned message if the destination is a port id.
In the programmer's guide, it mentions that TIPC_DESTNAME is created
when used using a TIPC name or name sequence. So those two
cases are covered for returned messages, but what about when we send a
message using a TIPC Port Id?
Excerpt from the programmer's guide under the recvmsg section:
Each of these objects is only created where relevant. For example,
receipt
of a normal data message never creates the TIPC_ERRINFO and TIPC_RETDATA
objects, and only creates the TIPC_DESTNAME object if the message was
sent
using a TIPC name or name sequence as the destination rather than a TIPC
port
ID.
Thanks,
Felix
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
