|
A RESTful API is a make-or-break feature for me and I'm sure plenty of other users or prospective users would love to see one implemented as well. It's mentioned in the issue tracker here: OSQA-345 but hasn't been assigned (I'm a mobile developer as well). Someone also mentioned that they've rolled their own in this question: Is an API available for OSQA but, as far as I can tell, never shared the code. I'd be willing to try and implement it myself using piston, but resources are limited so it depends on how difficult and time-consuming it would be. Has anyone attempted this? If you have, it would be great if you could share your thoughts or notes! |
|
I think, and this is just a thought, that the development of an API for this software might not be something in the best interest of the OSQA parent company, at least not a priority, given that this kind of features could undermine the appeal of its enterprise commercial product QATO. However this does not mean that an effort to fund and build an API could not be taken by the community and done collectively. A good project manager, a good team of developers and donations by the rest of the community could make this a reality. The tools and elements are there. Anyone wanna build upon this idea? Thoughts? |
any new news about an API
refreshing question..