[Catalyst] The state of (JSON|XML)-RPC modules

[Jose Luis Martinez]

Hi,

	I'm trying to get JSON/XML RPC support into a Catalyst app, and I'm 
seeing that the state of the different plugins, at best, is 
unmaintained, and all of them seem to be broken...

	We have a couple of applications that were using 
Catalyst::Plugin::Server::XMLRPC from debian Etch/Lenny packages. In 
squeeze, it is not included (It doesn't seem to work in Cat 5.8). So I 
decided to go an fix it.

	Trying to understand what is broken in that module I stumbled across 
Catalyst::Plugin::XMLRPC and Catalyst::Plugin::JSONRPC: the two 
broken/unmaintained.

	So... I've been playing around with them in github 
http://github.com/pplu/Catalyst-Plugin-Server, and have these results:

	- Catalyst::Plugin::XMLRPC: Working again :). It needed:
           - update NEXT to MRO::Compat
           - the Action('XMLRPC') was not working. Changed it to be an 
ActionClass('XMLRPC'). Was this the correct move?


	- Catalyst::Plugin::JSONRPC : It's now fixed. It needed:
           - update to JSON 2.X API calls
           - update test to not use [MVC] naming
           - Change the way the plugin was getting the method to call: 
http://github.com/pplu/Catalyst-Plugin-Server/commit/3e79e0b8a3176ff32c6a8c658c24116366bb6986. 
I'm not sure if this is the correct way to do it (feedback welcome).

         - Catalyst::Plugin::Server : Not working (yet)
           - updated the calls to MRO::Compat style


	All of this has brought me a couple of questions to mind: if these 
modules are actually not working: have I not seen a module that is 
maintained and working? Is there no interest in JSONRPC and XMLRPC these 
days? (no need to update apps that used these modules?)
	
	Also: help is welcome. If you have a hint of what is wrong with 
Catalyst::Plugin::Server, please feel free to tell me so...

Best Regards,

Jose Luis Martinez
jlmartinez at capside.com