I have been using xmlrpc++ for a week or so and I think it is awesome! After fiddling with SOAP for C++ I can't believe how much easier this is.
That said I think there are 2 things that are vital additions for the library for most realworld use.
1) Threads on the server. At least the server process should run in its own thread so an application can do other things too. Spawning a new thread for each request would be ideal though.
2) SSL seems like a must have to me for any secure application.
Bonus) A Mac OSX version would be cool too.
Unfortunately I am not proficient enough to tackle any of these issues myself ;) I am currently using wxWindows with xmlrpc++ which has crossplatform threading functionality but I didn't think mixing the 2 codebases would be such a good idea.
Is anybody working on these issues?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been using xmlrpc++ for a week or so and I think it is awesome! After fiddling with SOAP for C++ I can't believe how much easier this is.
That said I think there are 2 things that are vital additions for the library for most realworld use.
1) Threads on the server. At least the server process should run in its own thread so an application can do other things too. Spawning a new thread for each request would be ideal though.
2) SSL seems like a must have to me for any secure application.
Bonus) A Mac OSX version would be cool too.
Unfortunately I am not proficient enough to tackle any of these issues myself ;) I am currently using wxWindows with xmlrpc++ which has crossplatform threading functionality but I didn't think mixing the 2 codebases would be such a good idea.
Is anybody working on these issues?