Christian, as always I find your thoughts interesting. I don't know how far you and Martin carried the topic, but here are a few thoughts of my own regarding this.
Remote data binding with an end-to-end solution would require a server-side component. This is certainly a reason for us to treat this cautiously, as we want to stay "server-neutral". Of course you could always (and probably should) provide a reference implementation for the server component, and leave it to others to do the same for other server platforms. But we would still enter a new area with all its consequences, maintaining the code, providing demos, providing a runtime environment for it on one of our servers and so on and so forth. All things that would go on top of our existing work load and targets. (My gut feeling is this is much more than just some man-hours, as you put it, more like half an FTE for some time). The alternative that I see for us is just establishing a protocol and provide the client bindings for it. This way we could focus on client code. We would still use server components, but only for us internally, for developing and testing, and without publishing any of it. Much like with RPC. So is there an existing design, an existing architecture how to put up remote bi-directional data binding? Could we use existing protocols, like RPC? Would it really make sense outside a Websockets setting? Have you any insights to share here? T. > Hello, > > I have already talked to Martin about this topic off-list: > > I know that remote databinding is not a priority at 1&1, but think it > would > be really important that the company reconsiders its position: if qooxdoo > supported remote bidirectional real-time databinding natively (or via some > third-party libraries), this would enhance the toolkit's value immensely. > Many apps that are really useful and would have a market immediately > spring > to my mind (for example, a cool IMAP mail client, enhanced feed reader, > all > kind of other collaborative tools). The lack of this feature is one main > reason why I don't continue to enhance my own app - because it would take > me > too much time thinking about how to implement it. And would 1&1 itself see > the potential of this technology for its own in-house apps? > > I wonder if anything could be done to convince management to invest some > man-hours into developing this feature. > > Thanks, > Christian > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/How-to-remote-data-binding-for-widgets-in-general-tp7366145p7381261.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
