> >with the external program i have a situation like this: > >runtimeA(); //prepare the widget for the rappresentation of the stdout >runtimeB(); //call the server object and launch the external program > >At the moment the widget for runtimeA appear only after the runtimeB() >is finished, i don't really understand why.
This is because either because Qooxdoo hasn't recalculated the layout of the widgets yet or because the browser hasn't updated it's display when you make a synchronous call - either the way the effect is the same: client apps are single threaded and that includes the browser redrawing the display. Making a synchronous call blocks the one thread. If you have a long running process and you don't want the client to block, you'll have to poll the server - at the moment there is no facility in QSO to have an asynchronous method call. This would mean running your external server process in a separate thread and your runtimeB() method would check to see if there is any fresh output from the external process and if so return it. You will have to manage your own synchronised calls to that thread. >I see also that if i don't use the interface, after some time, the >session expires, this is a good point, but how i can interface with the >session? This is a normal issue - if you are finding that your session times out and Tomcat destroys the session you can either increase the session timeout (I think the default is 20 minutes) or you can "ping" the server every few minutes to keep it alive -- but that could mean that your client leaves their session open forever and will permanently use up server resources. You can install a keyboard and mouse callback on the document to check for user activity - and only ping the server if the user is still actually active. >i need to build also the authentication for my application, >there is some function to controllor the session with the serverobject? Nope, that's up to you. >For the query to the db i have a similar problem, when press the button >for start the query, the botton stay pressed until the query finish. At the moment, the only solution is to poll the server for long running requests. Is your database really huge or complex? Can you look at optimising the query, adding indexes, etc? (sorry, I know that doesn't solve your problem but it might be something worth doing anyway and could help here) John ------------------------------------------------------------------------------ 5 Ways to Improve & Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
