Hi, Robin,

Thanks for the comments. I'm just going to try to give you hope that
the future will be better :) and ask a couple of questions.

> CherryPy
> ========
>
> It's slow and doesn't allow me the fine-grained control
> I need for my web projects.

FWIW, CP 3 (fast approaching beta) is about twice as fast as CP 2. I'd
be very interested to know more about what you mean by "fine-grained
control". Now is the time to get feature requests in. ;)

> No obvious easy way to do URL rewriting. And no
> controller.default() doesn't count.

CP 3 will have full support for custom dispatchers, like Routes or
Django-style regexes.

> I think the sluggishness is mostly because it's written
> in Python. Also I can't find a good way to let it handle
> multiple requests at a time. I wrote an AJAX in-house
> tool recently. It aggregates data from a website using
> BeautifulSoup. There's an option to aggregate lots of data
> at the same time, which it achieves by doing lots of
> XMLHTTP requests. CherryPy doesn't seem happy with
> doing more than 2 processes at a time, even with
> thread_pool increased. There could also be a locking
> issue. I'm pretty sure this isn't related to FF's
> "max connections/server" features - I'm aware of
> those. I know a similar PHP tool works fine.

These are always hard to address because the locking issue might be
completely outside of CherryPy; I've heard scattered reports of locking
issues but haven't been able to reproduce them. If there's any way you
could demo the problem, I'd be *very* glad to review it.

C'mon back someday!


Robert Brewer
System Architect
Amor Ministries
[EMAIL PROTECTED]


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to