Michael, I probably need more time to digest this email, to fully
understand your architecture.
Our own application architecture (in production since 2011) looks like this:
Java backend -> Redis -> NodeJS -> Faye -> Flex (with MXML data binding)
New architecture:
Java backend -> Firebase -> Webix
(Webix chosen for the reasons outlined in the previous email).
However, because Webix has no concept of MVVM, we are developing a
layer to subscribe to firebase and look up the view components. As you
know, the code complexity increases significantly without an MVVM
pattern. Also, there is the whole coordination issue of making sure
that Dom elements before being changed! (again, obviated with MVVM
binding patterns).
So, in summary, using GluJs to bind Webix would seem to be a win.
Dave
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GluJS" group.
> To unsubscribe from this topic, visit
>
https://groups.google.com/d/topic/glujs/cGYA5kgU718/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
>
glujs+un...@googlegroups.com.
> To post to this group, send email to
gl...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/glujs/7e4147bf-4754-4401-bbd4-d002702faa85%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.