Qt DevNet Web Service API
-
Gurudutt, another problem today. Onthe front page again, line 226, col 181:
@
<div class="item"><img src="http://developer.qt.nokia.com/uploads/qt_quarterly/qt_ambassador_logo.png" alt="Qt Ambassador" width="150" height="201" alt="image" /></div>
@the alt attribute is redefined leading to another error when using XQuery on that xhtml. Could you squash that bug too please? It looks like a simple static html one.
Many thanks.
-
[quote author="ZapB" date="1304592956"]Gurudutt, another problem today. Onthe front page again, line 226, col 181:
the alt attribute is redefined leading to another error when using XQuery on that xhtml. Could you squash that bug too please? It looks like a simple static html one.Many thanks.[/quote]
It should be fixed now.
-
Yup. Thanks for the swift turnaround.
At the risk of telling you guys how to do your jobs it might be an idea to integrate a call to xmllint to catch these types of errors at source. Could be doen as part of your CMS' add new content function perhaps? Please don't take that as criticism, it's just a polite suggestion. I think you are all doign a great job. :-)
-
Hi ZapB
The way we have prepared Qt Developer Network,
in that some content's are added/edited by editors and some of them is fetched from mysql database via CMS api.The things I have fixed for this issue, I am not sure if in future it will not occur again since some of our editors might not be that technical to think about all these standards.
About giving access to admin site, I am not sure if that is ideal, I guess there are some security concerns and many more.
We wish to make all Qt Developer Network source as open source one day but we want to evaluate all security concerns before doing it.
I guess for your concerns qtapi would be best in future, it is disabled for now, but we wish to open it as soon as we can.
In future we wish to have better solution for qtapi for better performance.
-
[quote author="Gurudutt" date="1304609532"]Hi ZapB
About giving access to admin site, I am not sure if that is ideal, I guess there are some security concerns and many more.
[/quote]Although it might solve some problems, it should be fairly obvious that we can't do that. We're even carefully towards our own colleagues.
Just imagine someone accidentally hitting the "drop all tables" button. :P
-
Hi Gurudutt,
Oh I wasn't suggesting that we all have access to the admin side. I was just saying earlier that if the CMS happened to be open source I could take a look at adding functionality to properly escape xml entities. Since it is not, then no problem. I'll leave it to you guys and gals.
My previous message was just suggesting that to help non-technical content writers, running the submissions (well the page that would result from a submission) through xmllint or some other validator before accepting the submission might help catch these simple errors. Modern browsers will happily process xhtml even with such errors but an author could still potentially break the page with a bad submission.
I realise that long-term using QXmlQUery is not the best way to get info about QtDN and that the REST API is the way to go. But until it is updated or even better, opened up, then we are limited as to what we can do with it.
If the CMS code, and SQL scehema (but not auth details etc) were placed on gitorious we could even help develop the REST API too and make MR's for it. Then you trolls can test the MR's in a sand-boxed environment and merge them only when you are happy with them.
Maybe a topic for discussion at the contributers summit?
-
[quote author="Alexandra" date="1304609933"][quote author="Gurudutt" date="1304609532"]Hi ZapB
About giving access to admin site, I am not sure if that is ideal, I guess there are some security concerns and many more.
[/quote]Although it might solve some problems, it should be fairly obvious that we can't do that. We're even carefully towards our own colleagues.
Just imagine someone accidentally hitting the "drop all tables" button. :P[/quote]
I never suggested having access to the admin side of the live site - only the source code of the CMS. ;-)
-
As for making the API faster, you could use mod_rewite or some other method to redirect the API requests to a dedicated box that runs a Qt/C++ mini-webserver process that uses all those lovely Qt modules to query and process the requests into a suitable json response. All we need to get that off the ground is some details of the database schema. We could open it up as a QtDevNet community project ;-)
-
[quote author="ZapB" date="1304592956"]Gurudutt, another problem today. Onthe front page again, line 226, col 181:
@
<div class="item"><img src="http://developer.qt.nokia.com/uploads/qt_quarterly/qt_ambassador_logo.png" alt="Qt Ambassador" width="150" height="201" alt="image" /></div>
@the alt attribute is redefined leading to another error when using XQuery on that xhtml. Could you squash that bug too please? It looks like a simple static html one.
Many thanks.[/quote]
Hi ZapB,
Front page of Developer network follows XHTML 1.0 strict standards now.
Please confirm if it works as expected for your plug-in. -
[quote author="ZapB" date="1304332586"]Marius, I wonder if you could help me with something please?[/quote]
Hey ZapB, I'm back, adding the gravatar info should be doable, I suggest it becomes part of the next version of the API. See "this post":http://developer.qt.nokia.com/forums/viewthread/5451/P15/#35854 for my motivation.
-
Nothing new but a few days ago we added the devnet API documentation with examples here:
http://developer.qt.nokia.com/groups/devnet_meta/wiki/API_documentation
-
Marius, I think URL on the wiki should be "/qtapi/1/member/profile" instead of "/api/1/member/profile"?
-
On a side note, the QWebService lib I am writing (some of you might remember it from qt5-feedback) is now ready for RESTful, JSON web services. I've recently put together an example that users QtDN API. Getting JSON reply is doable with 1 line of code (although I use 3 lines in my example app). Available on "Gitorious":http://gitorious.org/qwebservice and, in the future, maybe as part of Qt5. I'll probably post more info on it in the future, in a separate thread. Sorry for any typos, I'm using my phone for this post.
BTW: Would appreciate any feedback on API, intuitiveness, usability etc., as well as help in coding.
