On 5/30/13, Gary Martin <[email protected]> wrote: > On 29/05/13 21:14, Antonia Horincar wrote: >> Also, I want to share what Shiva Teja (also a member of this mailing >> list) suggested to me yesterday. He wanted to share with me his idea >> on implementing the back-end of the project, which implied using >> IRequestHandler for dealing with web requests and the TracTicketSystem >> class to get the content of a specific ticket. Can anyone give some >> feedback on this, as I want to make a comparison between this approach >> and the one involving RestOnTrac, and choose the best one? >> >> Here is some documentation on IRequestHandler and TracTicketSystem: >> http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.IRequestHandler >> http://www.edgewall.org/docs/tags-trac-0.12.4/epydoc/trac.ticket.api.TicketSystem-class.html >> >> Thanks, >> Antonia > > Hi, > > Personally I would probably be going with using the IRequestHandler > route. It may be a little harder work but depending on RestOnTrac as > something that we don't know will be part of the default bloodhound > installation or will be available in time. >
I honestly do not think the better way is to reinvent the wheel . If not using RestOnTrac REST API then fallback to RPC plugin , The following fork is well tested (branch = bloodhound_rpc) https://bitbucket.org/olemis/bloodhound-rpc the only difference between both candidates is the style and API access pattenrs . Besides ... http://stackoverflow.com/.../what-is-the-best-javascript-xml-rpc-client-library http://code.google.com/p/json-xml-rpc/ http://json-rpc.org/wiki/implementations#JSON-RPCimplementation https://github.com/datagraph/jquery-jsonrpc http://code.google.com/p/json-rpc http://stackoverflow.com/questions/11600064/using-jsonrpc-with-jquery http://jabsorb.org/ ... amongst others ;) -- Regards, Olemis.
