I did investigate writing a plan9client for Jira earlier this year. it exposes its apis as soap, xmlrpc and rest so i could use any. from the little i have read rest looks preferable though i speak from a position of little knowledge here.
i hoped to write a genetic REST 9p file server that would allow you to send and receive simple requests via a virtual file, in the style of webfs. i have a DOM model xml parser that i used in wdfs (webdav fs) in my contrib that i planned to reuse. the advantage, of course, is the restfs could be reused for ups, fedex, jira, etc. sadly this got no further than a thought experiment due to work pessures, and recent family pressures (twins born last week) could also slow progress... -Steve On 31 May 2012, at 07:23 PM, Anthony Sorace <a...@9srv.net> wrote: >> The published APIs didn't seem to lend themselves to a >> simple screen-scrape. > > Well, they're mostly XML/SOAP, which is a pain, but they're not too rough as > such things go. Certainly they change a lot less than the web pages do, so > even if you're just using exactly the same techniques on what's returned it > should be an improvement from a reliability perspective. UPS's seem a bit > better than FedEx's (I don't recall looking at USPSs). FedEx has a "web > integration" thing which might be easier to use here, but I don't know > details. > > If you don't want to do that, I think the only other option is another round > of > updating the HTML scraping that's there now. > > Anthony >
