On Tuesday 18 June 2002 11:58 am, Jeff Johnson wrote:
> So would there be much of a performance hit to replace HTTPResponse's
> write with the one in Page? �And could we add writeln while we're at
> it?
Jeff, my idea was to keep HTTPResponse's write() as fast (and
therefore, as simple) as possible for performance reasons, and to put
conveniences in Page. I have actually seen pages speed up by putting
self.write = self.response().write in awake().
The other reason, is that if someone has different approach to such
conveniences, they can subclass HTTPServlet and provide an alternate
approach. e.g., Page is convenient, but if you want to take another
route, you can.
I plan to leave it that way.
Also, some complexities come up. To write out a dictionary, you really
need to HTML encode it or <objects will not show up>. But should
strings be encoded? Or what of objects whose str() is intended to be
HTML in the first place? The use of str() in Page is there mostly for
ints, floats, dates, etc.
Just some thoughts.
I see no reason the ExceptionHandler couldn't be made more robust, but
I'm confused by what happened. In cvs, line 130 writes
publicErrorPage() which should be a string based on what I see in the
code.
Can you take a closer look at that? What went wrong in your app? Also,
what version of Webware?
-Chuck
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
