Just to give some context we already have a the system working as multi-tier application however I'm now replacing the Swing GUIs with Qooxdoo/RpcServlet. The java servlet then talks to our application server to invoke the required named services.
omrihar wrote: > > Bharat - I meant that I just had to write too many handlers (to my > liking). > But I can make this work this way. > Fair enough. I wrote a Service qooxdoo object to encapsulate login(), logout() and service invocation (using named services and json arguments). I then wrote a bespoke Component object that ties a qooxdoo widget and the service parameters to populate the widget...and create any models/controllers along the way. You end-up instantiating the same rpc function handler (clojure) multiple times but each time you configure it for whatever service your app needs. This has really minimised the amount of physical code I've had to write for handling rpc. omrihar wrote: > > The only thing I find a little awkward is when I need to wait for windows > to be populated with values from the database, and I don't know when all > the lists are filled in, or don't have > the patience of handling multiple events that count until everything is > filled. > > I think that the number of users of the program will be quite small (~20), > which made me think that perhaps it would be permissible to use > synchronous > calls because I don't expect the server to lag much, but I guess that's a > big no-no... > I accept the advice given ie to only use async rpc. Our app server does a lot of caching so it will be very fast. However, my plan is to register each Component (mentioned above) with the screen it is in. Each Component will notify the top-level screen/window when its loaded and ready. I don't want to restrict the user so I'll just show some simple icon whether the screen is ready (ie all Components are loaded). TLDR: consider some application level objects to help manage the building/initialisation phase of your screen. cheers, Bharat -- View this message in context: http://qooxdoo.678.n2.nabble.com/RPC-calls-best-practices-tp5751398p5755527.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
