Have you considered to run two instances of your pyramid application and simply route the slow running tasks to the one and the rest to the other? There would be - no need need to rewrite code, - no danger the main applications blocks and - for the slow running app webservers have reliable connection queing
You could even use a session cache for communication of both pyramid apps. Arndt. 2013/1/28 Maarten De Schrijver <[email protected]> > Hello, > > I've written an application in Pyramid. In one particular view, I need to > connect to a kind of CRM system via SOAP-XML (need to check if the user > exists and if not add to this CRM system). It works fine, but, it is slow: > the users web browser "hangs" (or rather: is busy) sometimes for over 10 > seconds. > > How could I best solve this? I'm thinking along the lines of "handing > over" this particular task to another "application"? Or should I > investigate Eventlet and coroutines? > > Thanks in advance. > Maarten > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- DV Electric / Arndt Droullier / Nive cms cms.nive.co -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
