<div dir="ltr">Agreed, we could use Summer's table as start point and extract maybe more "concrete" use cases from it ? <div><br></div><div><a href="https://gist.github.com/secondsun/e6552abfbf51ed915d92#file-table-of-contents-md">https://gist.github.com/secondsun/e6552abfbf51ed915d92#file-table-of-contents-md</a><br>
</div><div><br></div><div><table style="border-spacing:0px;width:724px;display:block;margin-right:0px;line-height:25px;border-collapse:collapse;font-size:15px;overflow:auto;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;margin-bottom:0px!important;margin-top:0px!important">
<tbody><tr style="border-top-width:1px;border-top-style:solid;border-top-color:rgb(204,204,204)"><th align="left" style="border:1px solid rgb(221,221,221);padding:6px 13px">Use Case</th><th align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">
Push/Poll</th><th align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Realtime</th><th align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Server</th><th align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">
APIs Used</th></tr><tr style="border-top-width:1px;border-top-style:solid;border-top-color:rgb(204,204,204);background-color:rgb(248,248,248)"><td align="left" style="border:1px solid rgb(221,221,221);padding:6px 13px">Periodic Read Only Update</td>
<td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Poll</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">N</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">
Any legacy</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Pipelines, Authentication, Stores</td></tr><tr style="border-top-width:1px;border-top-style:solid;border-top-color:rgb(204,204,204)">
<td align="left" style="border:1px solid rgb(221,221,221);padding:6px 13px">Real Time Read Only Update</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Push</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">
Y(ish)</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Legacy + Updates for Unified Push</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Unified Push, Store</td>
</tr><tr style="border-top-width:1px;border-top-style:solid;border-top-color:rgb(204,204,204);background-color:rgb(248,248,248)"><td align="left" style="border:1px solid rgb(221,221,221);padding:6px 13px">Simple Settings Sync</td>
<td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Push</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Y(ish)</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">
Legacy + Updates for Unified Push + Updates for conflict mgmt</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Pipelines, Authentication, UnifiedPush, Store</td></tr><tr style="border-top-width:1px;border-top-style:solid;border-top-color:rgb(204,204,204)">
<td align="left" style="border:1px solid rgb(221,221,221);padding:6px 13px">Real Time Text Sync</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Push</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">
Y</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">Needs lots of custom code, vert.x realtime component</td><td align="center" style="border:1px solid rgb(221,221,221);padding:6px 13px">UnifiedPush, Store</td>
</tr></tbody></table></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 10, 2013 at 8:45 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">Sorry because I got lost into this thread, but do we have any use case scenarios to understand which problem we are willing to solve?<br>
<br>
I think would be nice to start to enumerate at least 3 and choose 1 to stay focused. Thoughts?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
abstractj<br>
</font></span><div class="im HOEnZb"><br>
On December 10, 2013 at 3:59:45 PM, Summers Pittman (<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>) wrote:<br>
> > The difference is we have different opinions, use cases, and<br>
> ideas of "correct". Our users will also have said ideas so our<br>
> solution should make it possible for both to be supported (even<br>
> if we only provide one).<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<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></div>