good point!
This somewhat leaves it open to ag-node-demo, etc. as well
+1 to 'aerogear-jaxrs-demo'
On Tuesday, October 8, 2013, Bruno Oliveira wrote:
I would say aerogear-jaxrs-demo, basically the goal is to expose the
same endpoints already exposed by ag-controller-demo.
> Lucas Holmquist <mailto:lholmqui@redhat.com <javascript:;>>
> October 8, 2013 11:41 AM
>
> On Oct 8, 2013, at 10:25 AM, Sebastien Blanc
<scm.blanc@gmail.com<javascript:;>
> <mailto:scm.blanc@gmail.com <javascript:;>>> wrote:
>
>> Hi,
>> Following the discussion we had yesterday during the team meeting
>> about the aerogear-controller-demo repository I've created this
>> jira
https://issues.jboss.org/browse/AEROGEAR-1327
>>
>> Maybe we could also use this thread to sum up what we need to expose
>> as rest endpoints in the new repo :
>>
>> * auth : to test login / logout / enroll
>> * simple CRUD endpoints : to test paging (and implicitly the pipes)
>> * a OTP related thing endpoint
>>
>> Did I miss something ?
>>
>> Let's also start a poll on the repo name :
>>
>> * aerogear-backend-demo
>> * aerogear-backend-support
>
> Is this really an AeroGear specific backend. maybe just
> javaee-backend or something, then we could have a node-backend, others
>
>>
>> ideas ?
>>
>> Seb
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org <javascript:;> <mailto:
aerogear-dev(a)lists.jboss.org <javascript:;>>
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org <javascript:;>
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj