<div dir="ltr">+1 on tagging current MASTER => 0.1.0<div><br></div><div style>+1 for merging the "endpoint-security" to master, afterwards</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 18, 2013 at 6:05 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">TAG is good :) <div><br></div><div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Jun 18, 2013 at 6:02 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">Yes, the work from the security branch.<br>
<div><br>
Matthias Wessendorf wrote:<br>
><br>
><br>
><br>
> On Tue, Jun 18, 2013 at 5:13 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a><br>
</div><div>> <mailto:<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>>> wrote:<br>
><br>
> 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>
><br>
><br>
> are u talking about the REST API doc (this thread)<br>
> or the (real :-)) work I did for security branch ?<br>
><br>
><br>
> Just let me know.<br>
><br>
> Karel Piwko wrote:<br>
> > On Tue, 18 Jun 2013 16:26:26 +0200<br>
</div>> > Sebastien Blanc<<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a> <mailto:<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>>><br>
<div>> wrote:<br>
> ><br>
> >> +9006<br>
> >> And we should check that the integrations tests are always in<br>
> sync with the<br>
> >> cookbook (use the same use cases / data) .<br>
> ><br>
> > Asciidoc provides a nice feature of including snippets of code<br>
> from real<br>
> > files into documentation. Not sure if that would be possible with<br>
> making groovy<br>
> > syntax for integration tests nicely fitting cookbook syntax, but<br>
> might be worth<br>
> > investigating ;-)<br>
> ><br>
> ><br>
> >> Seb<br>
> >><br>
> >><br>
> >><br>
> >> On Tue, Jun 18, 2013 at 1:54 PM, Matthias<br>
</div>> Wessendorf<<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>>>wrote:<br>
<div>> >><br>
> >>><br>
> >>><br>
> >>> On Tue, Jun 18, 2013 at 1:46 PM, Karel Piwko<<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a><br>
</div><div>> <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">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" target="_blank">matzew@apache.org</a><br>
</div><div><div>> <mailto:<a href="mailto:matzew@apache.org" target="_blank">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<br>
> 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<br>
> 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<br>
> 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<br>
> "message<br>
> >>> format + REST API"<br>
> >>><br>
> >>> I think in three different "chapters"<br>
> >>> * REST Management APIs (for creating PushApplication / Variant)<br>
> (+ 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<br>
> include other<br>
> >>>>> values/headers/params for the<br>
> >>>>> MobileVariant/PushApplication/Installation(aka<br>
> MobileVariantInstance) as<br>
> >>>>> well<br>
> >>>>><br>
> >>>>> -Matthias<br>
> >>>>><br>
> >>>> _______________________________________________<br>
> >>>> aerogear-dev mailing list<br>
</div></div>> >>>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
<div>> >>>> <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>
</div>> >>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
<div>> >>> <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>
</div>> > <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
<div>> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
> --<br>
> abstractj<br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
</div>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
<div>> <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>
> --<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" target="_blank">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><div>--<br>
abstractj<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></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>