Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
XML RPC for plugins?
dmoore:
thinking some more on this topic, at least in the short term I'm coming to conclusion that for my particular application using sockets makes the most sense:
1. supported in wxWidgets for windows and unix -- see wxSocketClient/wxSocketServer
2. supported in python in the standard libraries on windows and unix
3. simple API, just like pipes
4. unlike the implementation of pipes in python, bidirectional socket communication just works
5. I still get the option of remote communication
I can always port to something like ICE later on if I find I need the interface specification language, server side helper code etc...
MortenMacFly:
--- Quote from: dmoore on December 04, 2007, 10:38:35 pm ---I'm coming to conclusion that for my particular application using sockets makes the most sense:
--- End quote ---
You hopefully know what that means for users on Windows with a firewall? The firewall will start barking at C::B due to "phoning home" if you do so. This is not a no-go but keep in mind that C::B is often used by noobs that might just simply block the traffic or kill C::B and blame us writing viruses that phone home (to be dramatic). ;-)
dmoore:
Morten: I suspect this would apply to any RPC-based solution. I've seen the Netbeans IDE throw up firewall warnings, but that usually only happens once after installation. Would it be any different in the case of CB? Obviously users with more stringent firewall policies will have problems.
the bigger issue with a low level solution like piped processes or sockets is going to be dealing with unicode strings and other complex data types.
Game_Ender:
I have played around with ICE's Python and C++ versions on Linux. I can say they do indeed work, but I haven't yet used them in an application.
dmoore:
thought I'd return to this very old thread to say: xmlrpc++ for the win (http://xmlrpcpp.sourceforge.net/). far from perfect, but it gets the job done and I'm now looking at three (very crude) windowed python interpreters in my C::B session.
Navigation
[0] Message Index
[*] Previous page
Go to full version