| Use Case | Push/Poll | Realtime | Server | APIs Used |
|---|---|---|---|---|
| Periodic Read Only Update | Poll | N | Any legacy | Pipelines, Authentication, Stores |
| Real Time Read Only Update | Push | Y(ish) | Legacy + Updates for Unified Push | Unified Push, Store |
| Simple Settings Sync | Push | Y(ish) | Legacy + Updates for Unified Push + Updates for conflict mgmt | Pipelines, Authentication, UnifiedPush, Store |
| Real Time Text Sync | Push | Y | Needs lots of custom code, vert.x realtime component | UnifiedPush, Store |
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?
I think would be nice to start to enumerate at least 3 and choose 1 to stay focused. Thoughts?
--
abstractj
On December 10, 2013 at 3:59:45 PM, Summers Pittman (supittma@redhat.com) wrote:
> > The difference is we have different opinions, use cases, and
> ideas of "correct". Our users will also have said ideas so our
> solution should make it possible for both to be supported (even
> if we only provide one).
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev