Hi Vincent,

I think I saw your pull request on github. First of all, great work and I'd really like to get this into the remote control at some point.

However the JSON-RPC specification (1) does not allow for named parameters. The JSON-RPC (2) spec does.
Could you let us know if your improvements obey this specification ?



On Fri, Oct 18, 2013 at 12:53 AM, Vincent Biragnet <v.biragnet@minetmax.com> wrote:
Hi all,

Actually, I'm a freelance IT guy, mainly working with XML related technologies (e.g. my stackoverflow profile here: http://stackoverflow.com/users/780733/vincent-biragnet) and java.

I'm currently using limesurvey in a professional environment. I wanted to add features in the Remote control API and offer to share my dev with limesurvey community.

I'm working with the Json api, as recommanded in documentation.

I noticed that:
1) objects order in the "params" array has to fit params order in the function.
2) optional params may be mandatory. e.g.: if i need to pass the optional param number n, then optional param number (n-1) has to be defined in the json.

I made a pull request to fix those two problems (see here: https://github.com/LimeSurvey/LimeSurvey/pull/147)

Then I have some ideas to add features to export survey responses and statistics. For example: theĀ  export_responses_by_token may be extended to accept a list of tokens.

If you are interested in such work, let me know and don't hesitate to tell me if there are special rules or guidelines concerning the api.

Best Regards,

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
limesurvey-developers mailing list