Re: [Zope-dev] Any interest in a set of Zope products to supportCVS-versioned, XML/XSLT-based Zope development?

2001-10-31 Thread Romain Slootmaekers



> In our opinion, Zope
> is about a year or two ahead of where these guys are in many respects. 
>  Kudos!

When I asked the tomcat mailing list for Zope like functionality in tomcat
(some year ago) nobody even answered. The product probably wasn't known or
nobody saw the possibilities. I still think cocoon rocks, and 
session managament in Tomcat is way better than in Zope. The problem is
that Tomcat demands more skills from the webbies. and Zope allows easy
maintainance of 'live' sites, on site. Anyway,
 
> 
> The main problems we faced while moving to Zope were these:
> 
> - how to support version control, branching, merging, tagging, etc. 
> etc.  (we use CVS)
> - how to support our XML/XSLT-pipeline based document publishing 
> paradigm (cf Cocoon2)
Having moved ZZICT towards zope from jsp. we faced the same XSL/XSLT
problems. I often wondered: how come they have xml-rpc but not XSLT?


>
> XMLDocument:
> (Sorry for the name clash).  Inherits from CVSFile.Has a notion 
> of a "transformer" property that points to an XSLT transformer.
> This enables it to be rendered automatically into HTML when __call__ or 
> index_html is called.The underlying XML file
> can either be external or not.  The XMLDocument object represents the 
> entire file, as opposed to the parsedXML stuff that explodes
> a single document into multiple Zope objects for each XML node (correct 
> me if I am wrong...)

We developed more or less the same thingy: a ZZXML product which is an XML
file which upon rendering can be transformed by any number of XSLTs. the
way the XML and XSL are linked is that of the XSLT spec: 



...

I personally hacked in into a Zope 2.4 with the python xml.xslt and
xml.dom.ext packages and some 200 lines of glue code.

The problems with the thingy are:
- xml authoring :the xml documents are only editable as text
- xslt is not context sensitive. fi I'd like to be able to apply different
  style sheets for (fe) different authorization roles
- for some reason the webbies don't really like an XML/XSLT pipeline,
  because it is rather difficult to get the separation of concerns right.
  (fe content:XML only, first style sheet: structure of page second style
   sheet: markup elements , third style sheet: browser specifics aso)
  Web publishing still remains rather hard. 

> There is lots more to do, but we do have initial development versions of 
> all three working in the lab.   Is there interest in this kind
> of Product?   Would it be considered heretical? ;-)   Are others working 
> on the same thing?
In short: yes, donno, yes.

Romain.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Zope 2.4.2 DTML Method Bug

2001-10-31 Thread Casey Duncan

One of my products exposed a bug in the 2.4.2 version of DTMLMethod.py. It is 
minor and can be worked around, but I wanted to point it out:

Line 203 of DTMLMethod.py now contains:

del self.__dict__['validate']

which is part of a try...finally statement.

It seems that the "validate" key is not always present in the object at that 
point, specifically if you recursively call an object in a different context 
then it was originally called. as in:


  


This piece of code resulted in a KeyError on "validate" in my product code, 
which had previously worked fine. Perhaps another try statement should be 
wrapped around this del statement?

/---\
  Casey Duncan, Sr. Web Developer
  National Legal Aid and Defender Association
  [EMAIL PROTECTED]
\---/

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



RE: [Zope-dev] Zope & Cygwin

2001-10-31 Thread Norman Vine

Chris McDonough writes:

>I wanted to torture test the Zope
>session manager under the cygwin-built Zope using ab, which is good
>real-world threading test.  It appears that neither ab nor wget much like
>something about their communication with the cygwin-built Zope.  Here's a
>wget session with a cygwin-built python/Zope combo:
>
>--22:14:42--  http://localhost/
>   => `index.html'
>Connecting to localhost:80... connected!
>HTTP request sent, awaiting response... 200 OK
>2 Server: Zope/(unreleased version, python 2.1.1, cygwin) ZServer/1.1b1
>3 Date: Wed, 17 Oct 2001 02:14:42 GMT
>4 Connection: close
>5 Content-Type: text/html
>6 Content-Length: 3012
>7
>
>0K -> .. (freeze)

It appears as if this now works wit a locally compiled Cygwin DLL
  Cygwin CVS files < 2001-10-31 > 

wget now returns and I can now access the 'raw' Zope store 
with my editor via ftp :-))

Not really sure which patch, within the last 2 days, it was but ..

THANK YOU !

Norman


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Multi-threaded pcgi vs single-threaded pcgi

2001-10-31 Thread Remi Delon

Hi, I have a zope backend running behind an Apache server.
Up to now, I've been using the "standard" pcgi configuration.
Here is my understanding of what's happening (correct me if
I'm wrong):
  - When Apache gets a request, it calls pcgi-wrapper. If
the pcgi_publisher process is running, pcgi-wrapper connects
to it and gets the page. If pcgi_publisher is not running, pcgi-wrapper
first starts pcgi_publisher and then connects to it and gets the page.

Now, the problem I have with that is that pcgi_publisher is
single-threaded. I have to run long-running background tasks at night
to update my database, and I run them inside Zope. During that time,
the site is unavailable because Zope is busy executing what should
be a background task.

The solution I want to use is to start Zope in multi-threaded pcgi
mode, using the standard "Zope/start" script with the correct flags (-p)
This works fine, as long as I manually execute the start script. But
if Zope ever crashes, I would like Apache (maybe through pcgi-wrapper)
to automatically restart Zope in multi-threaded pcgi mode, when
someone requests a page.

How can I achieve that ?

Thanks.

RĂ©mi.


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.4.2 DTML Method Bug

2001-10-31 Thread Steve Alexander

Casey Duncan wrote:

> One of my products exposed a bug in the 2.4.2 version of DTMLMethod.py. It is 
> minor and can be worked around, but I wanted to point it out:
> 
> Line 203 of DTMLMethod.py now contains:
> 
> del self.__dict__['validate']
> 
> which is part of a try...finally statement.
> 
> It seems that the "validate" key is not always present in the object at that 
> point, specifically if you recursively call an object in a different context 
> then it was originally called. as in:
> 
> 
>   
> 
> 
> This piece of code resulted in a KeyError on "validate" in my product code, 
> which had previously worked fine. Perhaps another try statement should be 
> wrapped around this del statement?


This happens when a dtml method is reentrant.

The fix needs to be a bit deeper than what you describe above, otherwise 
you'll potentially lose the "validate" attribute of the dtml method 
object, and you'll get strange errors.

I've put this into the new collector, with a patch:


   http://new.zope.org/Collector/4

--
Steve Alexander
Software Engineer
Cat-Box limited


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Suggestion: Blocking out Localroles?

2001-10-31 Thread Lennart Regebro

Nobody has responded to this, so at least it's not obviously stupid. :-)
So my question ow is: How to I create a proposal? Is there a right you need
to have, because even when I'm logged in I don't see any obvious way of
doing it, and I can't find any instructions in any of the documents of how
to create the proposal.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] RAMCacheManager and gzip

2001-10-31 Thread Oliver Bleutgen

JanStiller T-Online wrote:

> Hi,
> 
> Is it possible to marry the RAMCacheManager and gzip?
> 
> I'm just working on a little shop and - for speed's sake - do 'ram-cache'
> the article-listings and push all the Zope-Content through mod_gzip. With
> this combination, I'm getting it 3x faster in Zope and 5x faster over the
> wire (normally 64k). That's great so far. But I don't see any sense in
> zipping cached content over and over, so I tried to zip the cached data in
> RAMCacheManager. 
> [...]


IMNSHO, mod_gzip does (can do) caching on its own (directives
"mod_gzip_keep_workfiles" and "mod_gzip_temp_dir"), and perhaps
it might work with mod_proxy in some intelligent way. Maybe
you might want to check this first before doing too much work.
Also be warned, there are certain kinds of documents which will
make problems when served compressed, like PDFs. While
you won't want to RAM-cached PDFs, it might occur that RAM-caching
and compressing do conflict.

cheers,
oliver




___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Any interest in a set of Zope products to support CVS-versioned, XML/XSLT-based Zope development?

2001-10-31 Thread Adrian Hungate

I'll leave the CVS to others, XML stuff is right where I am looking at the
moment. My XML kit is not "standards" based (And anyone who has spoken to me
about XMLKit will know that I don't like the current SAX/DOM implementations
in python as they try to make Python think like Java...). I have been
looking to greatly improve the proccessing in my XMLDocument because it is
currently both counter-intuitive and clumsy to use. I may have
misunderstood, but my XMLFile and XMLProxy objects my provide some of what
you were taking about with the Zope access to XML both inside and outside of
your Zope.

Maybe we can move XMLKit in the directions you are talking of aswell?

The two criteria that I have are:
1) The code needs to be Python, not C (For now at least) for the platform
independance. (A number of Zope products I would love to use will only run
on one platform and I need complete platform independance for most of my
installations).
2) The product needs to be easy enough to use that a someone who is not an
XML-guru can use it to good effect.

Adrian...

--
The difficulty of tactical maneuvering consists in turning the devious
into the direct, and misfortune into gain.
- Sun Tzu

- Original Message -
From: "Craeg K. Strong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 31, 2001 2:30 AM
Subject: [Zope-dev] Any interest in a set of Zope products to support
CVS-versioned, XML/XSLT-based Zope development?


> Greetings!
>
> We at Ariel have recently started using Zope and, needless to say, we
> are enjoying a large increase in productivity
> compared to our previous Apache-Cocoon2-Tomcat-Servlet-dbXML-Java
> environment.   In our opinion, Zope
> is about a year or two ahead of where these guys are in many respects.
>  Kudos!
>
> The main problems we faced while moving to Zope were these:
>
> - how to support version control, branching, merging, tagging, etc.
> etc.  (we use CVS)
> - how to support our XML/XSLT-pipeline based document publishing
> paradigm (cf Cocoon2)
>
> We have seen several efforts underway to address these issues within the
> Zope community.   We have gone a slightly different
> direction, but hope to contribute to these efforts in some way. In
> our environment:
>
> - multiple author/developers work on the same documents at the same time
> - we work on content for several clients at the same time
> - web pages are cobbled together from content pulled from several XML
> documents, according to a PagePolicy
>(similar to the way articles are collected and pasted into a
> newspaper page).
> - the PagePolicies can be changed independent of the underlying content
> (header-body-leftmargin-footer, header-body, etc)
> - all content is in XML, transformed into HTML/DTML by XSLT.
> - we use lots of tools other than Zope, so we want to keep our content
> in XML, not pickled Zope objects. (hold the pickles ;-)
>
> In order to make all this work, we created three Zope Products:
>
> ExternalFile:
> Points to a file in the filesystem.  Unlike ExtFile, it is not copied
> into a repository directory, but remains "in situ"
> Behaves similarly to a symbolic link in UNIX or windows shortcut.
> Metadata stays in Zope, but content stays in the file.
> index_html and __call__ return the content as if it were a real Zope
> object, so Zope doesn't know the difference. :-)
> Due to permissioning and other possible problems, this is probably only
> appropriate for development, not production.
> In future, we hope to add an option to copy in the content to ZODB,
> essentially converting it to a DTMLDocument.  At that
> point we will probably rename the class "ExternalizableFile"  more on
> this later.
>
> CVSFile:
> inherits from ExternalFile.Same thing, but the file is assumed to be
> inside of a CVS sandbox.   Includes buttons for doing
> normal cvs commands.   Sandboxdir is stored in a cookie, so each
> developer can access his own sandbox via THE SAME ZOPE OBJECT.
> That is, all developers can share a single Zope server but each see
> content from his own sandbox.   (play in your own sandbox :-)
> This avoids the locking issues and other problems inherent in things
> like CVSwebClient.   It also enables the content to
> stay "native" rather than becoming a Zope extract like in
> ZCVSMixin/ZCVSFolder.
>
> XMLDocument:
> (Sorry for the name clash).  Inherits from CVSFile.Has a notion
> of a "transformer" property that points to an XSLT transformer.
> This enables it to be rendered automatically into HTML when __call__ or
> index_html is called.The underlying XML file
> can either be external or not.  The XMLDocument object represents the
> entire file, as opposed to the parsedXML stuff that explodes
> a single document into multiple Zope objects for each XML node (correct
> me if I am wrong...)
>
> There is lots more to do, but we do have initial development versions of
> all three working in the lab.   Is there intere

Re: [Zope-dev] Multi-threaded pcgi vs single-threaded pcgi

2001-10-31 Thread Dieter Maurer

Remi Delon writes:
 > 
 > The solution I want to use is to start Zope in multi-threaded pcgi
 > mode, using the standard "Zope/start" script with the correct flags (-p)
 > This works fine, as long as I manually execute the start script. But
 > if Zope ever crashes, I would like Apache (maybe through pcgi-wrapper)
 > to automatically restart Zope in multi-threaded pcgi mode, when
 > someone requests a page.
There are supervisor scripts around (--> mailing list archives)
that continously check Zopes availability and restart, if it
becomes unavailable.

Not precisely what you want, but maybe sufficient


Dieter

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )