Noah Kantrowitz wrote: > Tammo van Lessen wrote: >> Hi devs, >> >> I recently stumbled upon trac.resource and was wondering whether this >> might be the corner stone for a RESTful API. Such an API would be >> really great to create issues automatically (e.g. for reporting failed >> integration builds) or to integrate Trac with things like Eclipse >> Mylyn. Yes, there is an XMLRPC plugin but as issue tracking is per se >> more resource oriented than service oriented, a REST API would be more >> natural and easier to use. >> >> A decent introduction to REST principles can be found at [1] (p24ff) >> and [2]. IMHO the trac architecture is almost ready for such an API, >> adding support for content negotiation, a Atom and/or JSON >> representation and support for the verbs PUT and DELETE (and slightly >> changed semantics for non-HTML-form POSTs), that's it. Most probably >> this sounds easier than it is... >> >> So back to my questions: Is such a thing on your (mid-term) road map? >> >> > As with XML-RPC, this will never be part of Trac core,
Who said that? -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
