update on wsgiserver: - as of today, I received a suggestion on reverting to a specific changeset; this changeset (one line effect for us) has potential to address the issues we see in new server;
- still plan to characterize more (tests, traces) before considering a change; look for request for general testing perhaps as soon as this weekend. Yarko On Tue, Jan 6, 2009 at 3:39 PM, Yarko Tymciurak <yark...@gmail.com> wrote: > FYI: > > On Jan 6, 4:44 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: >> > includes Tim's patch for winservice, latest wsgiserver (*) and latest >> > simplejson. >> > I am skeptical about (*) because I have had problems in the past. I >> > cannot reproduce those problems today (which I guess is good). >> > Please try them and let me know if you tried and whether or not you >> > encounter any problem. >> > > we are working this on the cherrypy list, have taken a few network traces, > and so far _think_ this possibly may involve some interaction with cherrypy > and mod_proxy on Apache (but not sure yet what the source is). > > Massimo has shifted cherrypy server on web2py.com, and I / we've got a few > traces. > > We'll continue testing tonight, and working with cherrypy folks as > necessary.... > > Stay tuned.... > > Yarko > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
