Jamie Heilman wrote:
Why make the unlucky user pay the price?
Because the unlucky user (which I read as: author) is the only one who
knows the required behavior of their code.
Allow me to clarify -- I meant the end user browsing the website.
I hate it when I surf to a less-highly-used port
> Why make the unlucky user pay the price?
Because the unlucky user (which I read as: author) is the only one who
knows the required behavior of their code.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** N
Hello:
I am getting ready to release the next version of XMLTransform, and in
revisiting the Caching strategy for the product, I realized there are larger
issues that probably deserve a discussion here.
The bottom line is that transforming XML to something else via
XSLT is a potentially expensiv
On Monday 03 March 2003 3:48 pm, John Ziniti wrote:
> Any ZODB developers read this article at /. and the accompanying
> one at developerWorks? Would anyone care to comment about
> the relevance/comparisons of "prevalence" to the concepts of
> persistence used in ZODB and/or ZEO?
I had looked at
Any ZODB developers read this article at /. and the accompanying
one at developerWorks? Would anyone care to comment about
the relevance/comparisons of "prevalence" to the concepts of
persistence used in ZODB and/or ZEO?
http://developers.slashdot.org/article.pl?sid=03/03/03/1220222&mode=nested&ti
Yo,
the response headers set in ZPublisher.HTTPResponse our not always RFC
compliant. In case of exceptions you get: (round lines 670 in
HTTPResponse.py)
if ev.find( '') >= 0:
ev = 'bobo exception'
self.setHeader('bobo-exception-value', ev[:255])
If the content is a xml,wml,wh
AFAICT, AdaptableStorage is designed to allow this kind of thing.
Shane?
Sounds interesting. I am going to search for this.
Yes, it is. I don't know anything about NetCDF, but it sounds
intriguing. I guess NetCDF is not just an encoding format, but also some
kind of database for large arra
