469,274 Members | 1,833 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,274 developers. It's quick & easy.

SOAP/XML-RPC data transfer for instant messaging application

Hi, i have been looking at SOAP and XML-RPC and it seems ideal for my

I am looking at an application with 2 end points, either of which can
send and receive data. I know with SOAP (and varients) that requests
are issued to a server rather than in a bidirectional manner which i
need. this has left me wondering how instant messaging software works
(i believe jabber can make RPC calls and uses SOAP)?

I dont want to poll the server to see if it has any data to send me, it
would be nice if i can get the server to send asynchronously. Whilst i
am writing the server side in C# i need to use a c++ compatible soap
libary for the other end as it will be going on embedded hardware at
some point in the future.

I currently have another system which opens up a TCP socket and sends
and receives xml packets between the two nodes asynchronously. My new
requirements are that an RPC can be made (for instance,
GetBatteryVoltage), with the response being returned in a well
controlled synchronous manner. With my current system i will need to
write additional software to allow me a request/response system like
the one i need (i dont want to reinvent the wheel)!

So to sumarise my main questions:

Is bidirectional RPC possible and has it been done before (i belive
jabber does this)?

I would prefer a tcp stream rather than HTTP (less overhead because no
web server), i would also like the connection to be persistant. Is this
possible? I may need to modify two different libaries (C# and C++), so
i may just have to live with HTTP because of time scales.

Is having a RPC server on each node a resonable solution? The only down
side is i need two connections. At least i could do RPC to both nodes
from either end, which is what i want!

Any pointers, tips or comments much appreciated


Nov 17 '05 #1
0 1397

This discussion thread is closed

Replies have been disabled for this discussion.

By using this site, you agree to our Privacy Policy and Terms of Use.