“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra
This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!
Do not issue bugs reports against versions earlier than 0.9.9.5
Security problem? Check the security section.
FS#422 - XML-RPC API
Opened by Chris Padfield (padders) - Tuesday, 14 December 2004, 07:34 GMT+1
Last edited by Florian Schmitz (Floele) - Monday, 31 December 2007, 18:48 GMT+1
|
DetailsThis is a follow up from the mailing list. Looking for an XML-RPC API that has the following features: - updating a user (password/profile etc) - creating a user
- logging in a user (ie so you can log a user into flyspray from another - getting details on a specific bug - getting a list of bugs given certain criteria (e.g. user, version number, unfixed status etc). - creating a bug from another product (e.g. for me, I get a support request in out ticket system, and will create a little window in that app with a “one click” send to bug interface.) |
Monday, 31 December 2007, 18:48 GMT+1
Reason for closing: Implemented in devel
Additional comments about closing: rev 1512 (JSON)
I’ve been a little bored on my holiday, so I started looking at this task. I have a basic xml-rpc server script working, and you can request a few different things from it; like task or user details.
Flyspray’s internals need a bit of re-working, moving a lot of stuff into functions so that they can be re-used by the main program or external scripts such as this. I’ll start on that after 0.9.7 is released. It will make implementing this task soooo much easier.
Why would you need to log someone in from another project? Can’t you use javascript and a hidden form to have a button that once clicked, logs the user into flyspray?
Or, simply have your application create appropriate cookies that Flyspray will recognise...
Btw, the XML-RPC interface currently has the ability to retrive details on a task, and close a task. More coming soon.
I will definitely appreciate this functionality as I will be coding up something that will need to submit new tickets. An XML-RPC interface to do this will really make this easier.
There have been a number of xml-rpc exploits lately, and the library we use hasn’t been updated in a couple of years. We need to switch to a library that has been secured against these recent exploits.
We now use the phpxmlrpc library from http://phpxmlrpc.sourceforge.net instead of IXR. Thanks to Angus Hardie for the patch on the mailing list.
What’s the current status of this? I know someone has done some stuff related do it, and it seems to have come up much more frequently on the mailing list lately.
See also:
FS#1156. Since no one is working actively on it currently, it is likely to be removed.Hang on. I sponsered this feature a long time ago paying Tony Collins a decent amount of money for its completion. Is he still working on flyspray?
Unfortunatley my real life situation now prevent me from working on the Flyspray project. This is why it has moved to the new server, and is now being managed by Florian. You are welcome to email me about the return of your sponsorship donation.
Christian suggested to reimplement such stuff with WSDL (that is web services) later again. We also intend to make it possible that you can interact with Flyspray over Jabber (and email). Maybe these could be alternatives.
this task has been marked as suspended cause a reimplementation needs to be discussed as well find a new mantainer.
Since nothing has been started yet (at least that's how it looks to non-developers), I think it makes sense to take a look at requirements/best practices for existing remoting solutions like Mylyn ( http://www.eclipse.org/mylyn/ ), which already integrates with Bugzilla, Jira and Trac (to certain degress).
Just found out such a request for Mylyn has already been denied, see
FS#1382. The response sounds reasonable as it's probably out of this projects scope to develop a Mylyn java connector.