<div dir="ltr">I agree with Summers;<div><br></div><div style>his 1) is a nice demo, while 2/3 are more test and RI. this can be just a bunch of services, that just behave different (for exception handling etc)</div><div style>
So the clients can use 2/3 to test their impl for positive and negative cases; and these "services" don't require a UI (like a demo). Just some endpoints</div><div style>to pump data against</div><div style>
<br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 22, 2013 at 6:45 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></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 Mon 22 Apr 2013 12:33:27 PM EDT, Sebastien Blanc wrote:<br>
> And keeping in mind we are going to demo a lot of other features like :<br>
> - Mulitpart support<br>
> - Data synchronisation<br>
> - Push support<br>
> So maybe this thread is also a good way of thinking about a new<br>
> showcase applicattion in which all these featurs could fit ...<br>
> Ideas ?<br>
<br>
</div>The way I feel we have three separate needs.<br>
<br>
1) A experience demo which shows off lots of functionality.<br>
2) A very stable set of services for clients to run tests against<br>
(ideally with stable data)<br>
3) A reference implementation of the service which says. This is what<br>
we want it to do. This will be the impl we look at when the spec is<br>
unclear on something and need a "right" answer.<br>
<br>
2 & 3 can probably be the same app. I feel like the experience demo<br>
should be something else. The last thing we want is a test suite<br>
creating 1000 objects and muching up everyone's demos.<br>
<div class="im"><br>
><br>
><br>
><br>
> On Mon, Apr 22, 2013 at 6:22 PM, Christos Vasilakis<br>
</div><div class="im">> <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a> <mailto:<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>>> wrote:<br>
><br>
> Hi team,<br>
><br>
> as we discuss in the meeting, we need a testbed app to go against<br>
> our integration tests for the nested path feature. For this there<br>
> are two options:<br>
><br>
> a) either enhance our currently TODO app and add support for<br>
> schemas of "/projects/{id}/tasks/{id}/tags{id}". Currently<br>
> ag-controller supports nested path params.<br>
><br>
> b) create a separate and simple app eg. a blog engine with<br>
> /blog/{id}/comments/id} etc. so that we point our tests there.<br>
><br>
> The advantage that a) gives is that we don't need to write and<br>
> maintain a separate app, but we may need some different behaviour<br>
> that doesn't cover either TODO or controller's functionality (eg.<br>
> upload file functionality on the Pipe etc). So I am more in b) so<br>
> that we can use it as a general testbed for the features we want<br>
> to implement (now and in the future.)<br>
><br>
> Wdyt?<br>
><br>
> Thanks,<br>
> Christos<br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
</div>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<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 class="HOEnZb"><div class="h5">><br>
><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>
<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>