Holger wrote:
>enesis (I don't know), I would be very careful when trying to access
> the routing socket layer across different protocol stacks. Unlike the
> binary-compatible IP/UDP/TCP APIs, the routing API was meant to be
> compatible across protocol stacks at the *source* level only, not at
> the binary level, i.e. the idea is that programs using it are
> recompiled for each new platform. That's because complex structures
> need to be exchanged in routing messages, and providing full binary
> compatibility across stack generations would be very difficult to
> design. That's why there is a version code (RTM_VERSION), to at least
> be able to detect mismatches at run time.
I was just using genesis when I ran the script, that is miami only,
and rxsocket.library test for miami running and warning the user
if he tries to use functions no availble in the current stack running.
The script was not intended to be used on multiple stacks.
Ciao. Alfonso.
____________________________________________________________
Genesis Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
