[Zope-dev] (no subject)
Title: We serve the infinite opportunities Uncover a priceless treasure The Compac's help center reports says that about 20% of the complains about pc trouble is just not plugged in computer. Likewise e-business. Is your business not working? Check it up that is surely plugged in. We offer you a unique business perspective with email and datamining technology - strategic insight inspired by technological expertise - to help you succeed in today's increasingly competitive environment. Email that Guarantees great Results, the pinpoint email addresses ! HIMSystem will give you infinite opportunities with state-of-art datamining technology. HIMSysem is collecting email addresses you want from all over the world. With the Stat-of-art dataming technology, we pinpoint the exact email addresses you want(valid prospects) and collecting them. With this,you can broadcast just the exact audience you want the most effective and speedy way. With our services you can contact real prospects(customers) directly and get opportunity to persuade a million(your choice) at once. Your opportunities expand world-wide. Do not compare with dummy email harvestor(email collector, just spam creator) which uses ordinary search engines. They are beyond comparion. HIMSystem is fully equipped with datamining engine, document clustering, knowledge discovery in DB scheme, ambidextrous automated robots, intelligent association rules and super performance email server(a million per hour) with full log analysis system. + World famous commerial database search(free). Our services are not only effective but also economical because we give you the email addresses themselves plus free 7 times sending. All services are fully offered seamlessly without additional prices. Services we offer We search and collect email addresses you want. Whatever you want, HIMSystm will find them through whole internet include commercial databases (such as Kompass, etc). We give you the email addresses themselves. You can keeping it yourself for later use. You can use our free 7 times free sending. Check the result objectively with log analysis system. You can check it everyday how many mail is sending, how many receive it and how many openings etc. Average time for services required: a week Prices and terms (special offer) Prices only 40 cents per each email address(minimum quantity 5000, volume discount available) free 7-times mass mail sending free opt-out mail management free log analysis free email consulting (check your emails by professional copywriter) How to contact Any questions and apply offers contact Executive Manager Kim, Nam Chul (email : [EMAIL PROTECTED] / Fax : 82-2-569-2211) EBookLeader is email specialized agency with IT professionals for ebook, datamining, email, intelligence processing. EBookleader, located in Seoul, KOREA, is supported by the state-run IT Industry Promotion Agency(KIPA) for its unique, guaranteed technology. Gil-Jap-Iee-media, which means guide or pathfinder, is the Korean name for eBookLeader. Haeam BD. 417, Daechi-Dong 983-3, Kangnam-Gu, Seoul, KOREA (Tel:82-2-554-7925 Fax:82-569-2211) Website : www.ebookleader.com / Email:[EMAIL PROTECTED] Our Deletion Instructions: We comply with proposed federal legislation regarding unsolicited commercial e-mail by providing you with a method for your e-mail Address to be permanently deleted from our database. Instructions: To be removed from this list, simply put Remove in the subject line and hit reply, or just click HERE. The email address you use to send it with will be immediately removed from our database
Re: [Zope-dev] improving str(REQUEST)
seb bacon [EMAIL PROTECTED] writes: Yes, I think you are right about collapsible trees getting in the way when debugging. Where trees are useful is when you don't know what you are looking for, i.e. newbies trying to understand Zope, so I think there's still a case for it. A short introduction (with link to the help system?!) and a small TOC with local links into the request at the top of the REQUEST representation may be more useful than a clickable tree. And easier to implement, too :) jens ___ 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] ParsedXML in Zclass methods loses permissions on Zope restart
Brad Clements wrote: I'm still casting around for a suggestion on where I can go to fix this. I have a ParsedXML object in the methods list of a ZClass Product. The Access Contents Information Permission Mapping always get's reset to blank in the ParsedXML object when Zope restarts. Is this a problem with ZClasses, or with ParsedXML? Taking a look at ParsedXML, it looks like it just does a very simple permission definition, so it doesn't *look* like there's something wrong there. What it sounds like is that something that should be persistent isn't for some reason. Either an object attribute is changed without the permission mechanism being informed of the change, or it's for some reason an attribute on a nonpersistent is changed. This at least would explain why the permission mapping magically goes away.. Don't know if that helped at all; good luck. If you find out there's any problem in ParsedXML please let me know! Regards, Martijn ___ 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: [Parsed-XML-Dev] Re: [Zope-dev] ParsedXML in Zclass methods loses permissions on Zope restart
Martijn Faassen [EMAIL PROTECTED] writes: Brad Clements wrote: I'm still casting around for a suggestion on where I can go to fix this. I have a ParsedXML object in the methods list of a ZClass Product. The Access Contents Information Permission Mapping always get's reset to blank in the ParsedXML object when Zope restarts. Is this a problem with ZClasses, or with ParsedXML? Taking a look at ParsedXML, it looks like it just does a very simple permission definition, so it doesn't *look* like there's something wrong there. What it sounds like is that something that should be persistent isn't for some reason. Either an object attribute is changed without the permission mechanism being informed of the change, or it's for some reason an attribute on a nonpersistent is changed. This at least would explain why the permission mapping magically goes away.. I don't understand the situation very well, but Martijn's explanation sounds familiar. Remember, there's only one persistent Zope object in a ParsedXML instance, and that's the document proxy object. All of the proxy subobjects are transient, and that includes proxy documents that are navigated to from proxy subobjects. I.E. if app.foo.PXML is the ParsedXML instance, then setting Zope attributes on app.foo.PXML.firstChild() and app.foo.PXML.firstChild.parentNode() won't persist. Same goes if you traverse to these nodes via the web-exposed URLs of these methods. Perhaps you're trying to persist changes to Zope attributes on those nodes? -- Karl Anderson [EMAIL PROTECTED] http://www.monkey.org/~kra/ ___ 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] improving str(REQUEST)
This sugestion gets my vote. Simple enough that it could be implemented without major work, transparent enough for people debugging, but making the REQUEST object more accessible to non-experts. I like! Adrian... -- The difficulty of tactical maneuvering consists in turning the devious into the direct, and misfortune into gain. - Sun Tzu - Original Message - From: Jens Quade [EMAIL PROTECTED] To: seb bacon [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 30, 2001 2:55 PM Subject: Re: [Zope-dev] improving str(REQUEST) seb bacon [EMAIL PROTECTED] writes: Yes, I think you are right about collapsible trees getting in the way when debugging. Where trees are useful is when you don't know what you are looking for, i.e. newbies trying to understand Zope, so I think there's still a case for it. A short introduction (with link to the help system?!) and a small TOC with local links into the request at the top of the REQUEST representation may be more useful than a clickable tree. And easier to implement, too :) jens ___ 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 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] 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 interest in this kind of Product? Would it be considered heretical? ;-) Are others working on the same thing? Thanks! --Craeg ___ 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] RAMCacheManager and gzip
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. In my first attempt, i replaced:
ZCache_get (RAMCacheManager.py):
entry.access_count = entry.access_count + 1
return entry.data
with:
entry.access_count = entry.access_count + 1
ob.REQUEST.RESPONSE.setHeader('Content-Encoding','compress')
return zlib.compress(entry.data)
The results:
1.
This works with Mozilla 0.96 only for very small entry.data. When I set
entry.data to 'XX', it works, but any real page gets
'htmlbody/html/body' as the result.
2.
This doesn't seem work in IE alltogether. (with 'Content-Encoding: gzip' -
zlib.compress != gzip!?)
I'm willing to spend some days of work for this feature, but although I have
2 years experience in Python I'm quite new to Zope and Internet-RFC's
and this is definitely a point, where I would appreciate some hints from
more experienced Zope-programmers (or a product, of course -- or the
statement, that this won't be possible... ;o)
regards
Jan Stiller
P.S. sorry, if my words seems a bit confused, I'm more used to reading than
writing english...
___
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?
You might want to look at the fishbowl project on this that was recently announced: http://dev.zope.org/Projects/Wikis/DevSite/Projects/ZopeVersionControl/ (URL copied from Brian Lloyd's earlier email - with a 7s delay in the AU-US net link at the moment, I can't check it's correct, unfortunately...) Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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 )
