Trac developers,

We're considering implementing an IRPCProtocol (http://trac-
hacks.org/wiki/XmlRpcPlugin) to provide a REST-style API
(http://en.wikipedia.org/wiki/Representational_State_Transfer).

We feel this would make it easier for people to integrate with our Trac
system, as it's a lot simpler than XML-RPC (at least from other
languages.) We also have some users of a REST API to our existing
ticketing system, and when we switch to Trac, it would be nice if they
had to make minimal changes.

>From our point of view, things which might encourage us to do this are:
 * We might be able to get close to compatibility with our existing
ticketing REST API (this is not published.)
 * Easier for new clients to be developed (REST-json is better known
than XML-RPC?) (We're mainly interested in "enterprise integrations"
here, but we're not much a fan of SOAP.)

However, we do not want our own implementation to diverge, so if we we'd
be trying to encourage take up of the REST interface in the wider
community, otherwise clients would generally end up using XML-RPC
anyway, for widest compatibility.

We wanted to post just to bring this up; we've not started work yet, but
may begin something on Trac-Hacks in February depending on response and
our own developer availability.

I think this was last discussed in 2008: 
http://www.mail-archive.com/[email protected]/msg02179.html 

Regards,

 Nick

-- 
Nick Piper MEng MIET RHCE| #define Joint Lead Architect
250 Brook Drive, Green Park, Reading RG2 6UA | United Kingdom
[email protected] | www.logica.com 
Logica UK Limited, registered in England & Wales (registered number 947968)
Registered Office: 250 Brook Drive, Green Park, Reading RG2 6UA, United Kingdom 


Think green - keep it on the screen.
This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you. 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en.

Reply via email to