<div dir="ltr">Understood, yes the meta object system could be facilitated for that. I have something similar implemented for my in-app protocol handler.<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">

On Thu, Dec 12, 2013 at 11:40 PM, Jason H <span dir="ltr"><<a href="mailto:scorp1us@yahoo.com" target="_blank">scorp1us@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div><div style="font-size:10pt;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif"><div><span>Close, more about using QObjects and QPROPERTYs to create a object hierarchy which map to slots. </span></div>

<div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif"><span><br></span></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">

<span>root = RestObject(NULL);</span></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">
<br>
</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif"><span>class O1 : public RestObject {</span></div>

<div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">Q_PROPERTY (QString p1 READ p1)</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">

}</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif"><br></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">

o1 = O1("o1", root);</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif"><br></div>

<div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">GET /o1/p1 (calls O1::p1())</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">

<br></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">Add
 QMetaObject magic for mapping query paramters to slot parameters</div><div><br></div><div style="background-color:transparent">GET /o1/p1?q1=6 (calls O1::p1(6))</div><div style="background-color:transparent">GET /o1/p1?q1=6&q2=7 (calls O1::p1(6,7))</div>

<div><br></div><div>add a PUT/POST for storage:</div><div>POST /O1/p2</div><div>7</div><div><br></div><div>calls O1::setP2(7)</div><div><br></div><div>etc. Basically REST services are object hierarchies, and we do that with QObjects (RestObjects)</div>

<div><br></div><div class="hm HOEnZb"><div style="background-color:transparent"><br></div>  </div><div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:10pt">

<div class="hm HOEnZb"> </div><div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12pt"><div class="hm HOEnZb"> <div dir="ltr"> <hr size="1">  <font face="Arial"> <b><span style="font-weight:bold">From:</span></b> Philipp Kursawe
 <<a href="mailto:phil.kursawe@gmail.com" target="_blank">phil.kursawe@gmail.com</a>><br> <b><span style="font-weight:bold">To:</span></b> Jason H <<a href="mailto:scorp1us@yahoo.com" target="_blank">scorp1us@yahoo.com</a>> <br>

<b><span style="font-weight:bold">Cc:</span></b> "<a href="mailto:interest@qt-project.org" target="_blank">interest@qt-project.org</a>" <<a href="mailto:interest@qt-project.org" target="_blank">interest@qt-project.org</a>> <br>

 <b><span style="font-weight:bold">Sent:</span></b> Thursday, December 12, 2013 2:46 PM<br> <b><span style="font-weight:bold">Subject:</span></b> Re: [Interest] What's next for Qt 5.3?<br> </font> </div></div><div><div class="h5">

 <div><br><div><div><div dir="ltr">Uhmm, what do you mean by providing REST Services?<div>Are you talking about a HTTP framework like Rails or Sinatra? Imho such functionality has no place in the default distribution of Qt. You can easily develop that as an addon library. In fact, to develop a basic REST HTTP Server in plain C++ with routes and handlers takes only a couple of hundred lines. With Qt it should be even less.</div>



<div><a rel="nofollow" shape="rect" href="https://github.com/pke/atlhttpd/blob/master/HttpServerImpl.h" target="_blank">https://github.com/pke/atlhttpd/blob/master/HttpServerImpl.h</a><br clear="none"></div><div><br clear="none">

</div><div>And can be used like this:</div><div><a rel="nofollow" shape="rect" href="https://github.com/pke/atlhttpd/blob/master/atlhttpd.cpp" target="_blank">https://github.com/pke/atlhttpd/blob/master/atlhttpd.cpp</a><br clear="none">



</div><div><br clear="none"></div><div>Is that what you have in mind?</div></div><div><br clear="none"><br clear="none"><div>On Thu, Dec 12, 2013 at 7:59 PM, Jason H <span dir="ltr"><<a rel="nofollow" shape="rect" href="mailto:scorp1us@yahoo.com" target="_blank">scorp1us@yahoo.com</a>></span> wrote:<br clear="none">



<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div style="font-size:10pt;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">

<div>

<br clear="none"></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">So now we have mobile off to the races...</div>



<div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif"><br clear="none"></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">



Is anything going to happen with making Qt a better network toolkit? By that I mean SOAP and rest services - and providing those, not just consuming
 them. Maybe a HTML5 canvas as part of QPA? WebGL for QML?</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">



<br clear="none"></div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif"><br clear="none"></div>

<div style="font-style:normal;font-size:13px;background-color:transparent;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif">

<br clear="none"></div></div></div></div><br clear="none">_______________________________________________<br clear="none">
Interest mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:Interest@qt-project.org" target="_blank">Interest@qt-project.org</a><br clear="none">
<a rel="nofollow" shape="rect" href="http://lists.qt-project.org/mailman/listinfo/interest" target="_blank">http://lists.qt-project.org/mailman/listinfo/interest</a><br clear="none">
<br clear="none"></blockquote></div><br clear="none"></div></div></div><br><br></div> </div></div></div> </div>  </div></div></blockquote></div><br></div>