<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 18, 2013 at 5:13 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What do you think about tag the current version and merge the security<br>
branch? Only if you want to we also can release the version 0.1.0 on<br>
maven central.<br></blockquote><div><br></div><div style>are u talking about the REST API doc (this thread)</div><div style>or the (real :-)) work I did for security branch ? </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Just let me know.<br>
<div class="HOEnZb"><div class="h5"><br>
Karel Piwko wrote:<br>
> On Tue, 18 Jun 2013 16:26:26 +0200<br>
> Sebastien Blanc<<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
><br>
>> +9006<br>
>> And we should check that the integrations tests are always in sync with the<br>
>> cookbook (use the same use cases / data) .<br>
><br>
> Asciidoc provides a nice feature of including snippets of code from real<br>
> files into documentation. Not sure if that would be possible with making groovy<br>
> syntax for integration tests nicely fitting cookbook syntax, but might be worth<br>
> investigating ;-)<br>
><br>
><br>
>> Seb<br>
>><br>
>><br>
>><br>
>> On Tue, Jun 18, 2013 at 1:54 PM, Matthias Wessendorf<<a href="mailto:matzew@apache.org">matzew@apache.org</a>>wrote:<br>
>><br>
>>><br>
>>><br>
>>> On Tue, Jun 18, 2013 at 1:46 PM, Karel Piwko<<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a>> wrote:<br>
>>><br>
>>>> On Wed, 12 Jun 2013 10:22:10 +0200<br>
>>>> Matthias Wessendorf<<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>><br>
>>>>> Hi,<br>
>>>>><br>
>>>>> a little doc about the REST endpoints:<br>
>>>>> <a href="https://gist.github.com/matzew/73ec38d853863e7bb1dd" target="_blank">https://gist.github.com/matzew/73ec38d853863e7bb1dd</a><br>
>>>> Extremely helpful, thanks! I wish I'd found it before I was wondering why<br>
>>>> unified push server started returning 201 instead of 200.<br>
>>>><br>
>>>>> I _think_ it would be nice IF the above "REST APIs" are also describing<br>
>>>> the<br>
>>>>> "params" and HTTP headers that are required.<br>
>>>>><br>
>>>>> These are currently (at least for sending) described in here:<br>
>>>>> <a href="http://staging.aerogear.org/docs/specs/aerogear-push-messages/" target="_blank">http://staging.aerogear.org/docs/specs/aerogear-push-messages/</a><br>
>>>>><br>
>>>>> What do you think?<br>
>>>>> Should we merge the "message format" spec with the "Sender REST-API"<br>
>>>>> endpoint documentation?<br>
>>>> Wouldn't they make a nice cookbook together if merged?<br>
>>>><br>
>>> +1000<br>
>>><br>
>>> I am currently on some security work, but I plan to merge the "message<br>
>>> format + REST API"<br>
>>><br>
>>> I think in three different "chapters"<br>
>>> * REST Management APIs (for creating PushApplication / Variant) (+ crud<br>
>>> workflow -> basically all used by the (future) Admin UI)<br>
>>> * REST Auth Endpoint (Login/Logout and "enroll")<br>
>>> * REST Sender (for sending push messages)<br>
>>> * REST "Device Registration" (for the MobileVariantInstances (aka<br>
>>> Installations))<br>
>>><br>
>>> That ensure the doc is not too long.....<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>>>> Also, if we do the merge.... I'd update the above gist to include other<br>
>>>>> values/headers/params for the<br>
>>>>> MobileVariant/PushApplication/Installation(aka MobileVariantInstance) as<br>
>>>>> well<br>
>>>>><br>
>>>>> -Matthias<br>
>>>>><br>
>>>> _______________________________________________<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>
>>>><br>
>>><br>
>>><br>
>>> --<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><br>
>>><br>
>>> _______________________________________________<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>
>>><br>
><br>
> _______________________________________________<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>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
abstractj<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<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>
</div></div></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>