I've asked IBM to consider publishing this on several occasions. I was wanting 
to create a client in PHP using their socket library.

I did get as far as tracing the network packets for a UniObjects connection, 
and it looks like someone with time to spare (ie. not me!) could work out the 
protocol: it looked pretty simple and unencrypted (so long as you don't use SSL 
of course).


Brian

> From: doug chanco
> on aix 5.2/ uv 10.2.x is it possible to directly talk 
> to the uvrpc without using uniobjects (ie. via a 
> direct socket call).  If this is possible can anyone 
> share how they did it (ie what did you send/receive) 
> or any special things you had to do to get it to work.

Any application that uses a socket expects specific sequences of
characters from a compatible client.  Unless you know that
protocol you won't be able to create a compatible client.  It
sounds like this is the spec you desire.  I don't think IBM has
published the API to the UVRPC interface and I doubt they would.

Unlike public protocols like Telnet, HTTP, SMTP, and hundreds of
others published as "RFC" documents, proprietary, closed-loop
protocols like UVRPC are rarely published, and don't need to be
because the one and only client should always be available.
Security concerns for the publisher (IBM) also would usually
discourage publication of the protocol details.

If you get the API for the client you could possibly create a new
compatible server using sockets.  This would allow any client in
the field to use your server instead of the default UVRPC server.
That opens all sorts of licensing issues.

In short, I don't think you'll get a solid answer to this.

So why do you want to do this?  Maybe another solution to your
primary problem is available.

Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to