<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 18, 2013 at 1:46 PM, Karel Piwko <span dir="ltr">&lt;<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, 12 Jun 2013 10:22:10 +0200<br>
Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org">matzew@apache.org</a>&gt; wrote:<br>
<br>
&gt; Hi,<br>
&gt;<br>
&gt; a little doc about the REST endpoints:<br>
&gt; <a href="https://gist.github.com/matzew/73ec38d853863e7bb1dd" target="_blank">https://gist.github.com/matzew/73ec38d853863e7bb1dd</a><br>
<br>
</div>Extremely helpful, thanks! I wish I&#39;d found it before I was wondering why<br>
unified push server started returning 201 instead of 200.<br>
<div class="im"><br>
&gt;<br>
&gt; I _think_ it would be nice IF the above &quot;REST APIs&quot; are also describing the<br>
&gt; &quot;params&quot; and HTTP headers that are required.<br>
&gt;<br>
&gt; These are currently (at least for sending) described in here:<br>
&gt; <a href="http://staging.aerogear.org/docs/specs/aerogear-push-messages/" target="_blank">http://staging.aerogear.org/docs/specs/aerogear-push-messages/</a><br>
&gt;<br>
&gt; What do you think?<br>
&gt; Should we merge the &quot;message format&quot; spec with the &quot;Sender REST-API&quot;<br>
&gt; endpoint documentation?<br>
<br>
</div>Wouldn&#39;t they make a nice cookbook together if merged?<br></blockquote><div><br></div><div>+1000</div><div><br></div><div style>I am currently on some security work, but I plan to merge the &quot;message format + REST API&quot;</div>
<div style><br></div><div style>I think in three different &quot;chapters&quot;</div><div style>* REST Management APIs (for creating PushApplication / Variant) (+ crud workflow -&gt; basically all used by the (future) Admin UI)</div>
<div style>* REST Auth Endpoint (Login/Logout and &quot;enroll&quot;)</div><div style>* REST Sender (for sending push messages)</div><div style>* REST &quot;Device Registration&quot; (for the MobileVariantInstances (aka Installations))</div>
<div style><br></div><div style>That ensure the doc is not too long.....</div><div style><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class="im"><br>
&gt;<br>
&gt; Also, if we do the merge.... I&#39;d update the above gist to include other<br>
&gt; values/headers/params for the<br>
&gt; MobileVariant/PushApplication/Installation(aka MobileVariantInstance) as<br>
&gt; well<br>
&gt;<br>
&gt;  -Matthias<br>
&gt;<br>
<br>
</div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>