- Zope-Dev - Zope lists

request.set
by Derek Quayle 11 Jun '01

11 Jun '01

I am fairly new to Zope and still coming to grips with it. Could someone please explain how this piece of code works  Cheers wabirdman

1 0

Cookie with dictionary as content
by florian_reiser＠gmx.de 10 Jun '01

10 Jun '01

Hi guys, I'm developing the ZPivotTable product. For implementing the drilldown mechanism, I need to store the information about which columns and rows are open in a cookie. I thougt of storing this information in form of a dictionary, which would be stored in a cookie. The dictionary consists of several lists, containing the open columns or rows. Could you give me a tip how i can store the dictionary in the cookie. I've already tried to converting it to a string and converting the string back, when needed. Greetings Florian -- ----------------------------------------------------------------------- | Florian Reiser PGP-Key:0x5368CF3F | | PGP-Fingerprint: 84C7 24BC F3A4 487F CBC7 692C 05DB 6E11 5368 CF3F | -----------------------------------------------------------------------

3 2

[Announce] API Documentation Fishbowl Project
by jimbo 09 Jun '01

09 Jun '01

Or how about this person? http://lists.zope.org/pipermail/zope-cmf/2001-June/007435.html oh oh a storm gotta go -jimbo

1 0

Re: [Zope-dev] Bulletproof ZCatalog proposal
by Shane Hathaway 08 Jun '01

08 Jun '01

On Thursday 07 June 2001 21:28, Phillip J. Eby wrote: > Yep. One of the last two times I spoke with Jim in person (either > the January DC visit or IPC 8, I forget which), he said something > about it maybe being a good idea to have some kind of priority system > like that. I'd love to see something like it exist, if it would make > some of ZPatterns' hackery unnecessary. Yes, I would too. I'm happy to see we're in complete agreement. > The implementation could consist of two subscription queues: > ruleAgents and indexingAgents. ZCatalog would register in > indexingAgents, and ZPatterns objects would register in one or the > other, usually ruleAgents. (I can think of some circumstances where > it would be nice to use the indexingAgents queue, but right now > ZPatterns apps have to work around this by defining their rules in > execution priority order.) Ah-ha, this is sounding familiar. You talked about rule agents and indexing agents in the ZPatterns wiki. > Upon being told to perform a transaction or subtransaction commit, > the transaction would notify all the ruleAgents, and then all the > indexingAgents. Objects could still subscribe to either queue while > this notifying is taking place. (So that triggered actions could > cause indexish objects to register as indexingAgents, not to mention > causing updated objects to fire additional triggers.) > > Once all agents in a queue are notified, that queue should be cleared > so that notifications are on a per-subtransaction basis. Once both > queues are cleared, normal transaction behavior goes forward. Would you say this would occur before tpc_begin() messages or just after? > Hm. That's simpler than I thought it was going to be. Shoot, I can > even see how to implement it as a runtime patch, that would've been > simpler than all the shenanigans ZPatterns goes through to fake out > the transaction machinery... and it's a better > implementation. Ah well. At the time I wanted to avoid trying to > convince Jim to add machinery to transactions "just" for ZPatterns, > given that ZPatterns wasn't a particularly established product at the > time. > > Let me know if you guys put something like this in, though, and I'll > definitely look at reworking ZPatterns to use the mechanism. It > could potentially cut a lot of code out and improve the robustness at > the same time. I don't foresee us adding this capability right away since we need to understand it better and it only applies to one working product and a hypothetical product. I'd suggest you go ahead with the runtime patch. Shane

3 2

] [Announce] API Documentation Fishbowl Project
by jimbo 08 Jun '01

08 Jun '01

--On Wednesday, June 06, 2001 11:50:43 AM -0700 jimbo <jimbo(a)tacomaplace.com> wrote: > I hope this helps. I wanted to add my feelings on the whole documentation > issue. It seems to me that the whole process caters around developers > too much. >>I have to disagree with you **in the context of this thread** for two >>reasons: Why disagree **in the context of this thread** at all? Alot of things change quickly in this field, so flexibility is a must to me. >> 1. DC has done a lot to improve the documentation for non-developers >> in the >> last year. The Zope Book(s) should have a major impact when they >>start to >> appear on shelves in the next month or so. My point >>Developer documentation has lagged behind. There still is alot of progress being made in that direction >> This thread is about a proposal to improve developer documentation. It says nothing at all about the other *existing* efforts by DC and others to improve other types of Zope documentation. I think you have a misunderstanding of freedom and opensource all in one topic. I'm don't follow you here since I know it helps to get feeback from users of a product. I'm talking about improving the API documentation. I seriously wonder how good that API is going to do me if I can't use it in the workplace today or next week. Everyday I see post like this http://lists.zope.org/pipermail/zope-cmf/2001-June/007427.html excerpt "I'm having trouble using the Guard expression in DCWorkflow 0.2. Everything else works fine; it's a great product. I think the call to expr() in the ...... I do not really know what I'm doing there... but it works :) " My point is Python is/was suppose to be this language so easy and simple that it should be the first language to teach a person. Where does that simplicity get lost with Zope I wonder? Don't even answer because it does'nt matter to me or the other it departments that are going with other solutions. So go on while the confusion is there. Go ahead and justify it now by saying polishing the API will do it for the masses. When you look at the big picture the developer is the smallest user group of any software product.( you have the end-user, testers, admins,etc) That's why it's even more important to make sure the API docs make it easy to implement something and not "wow this is so cool and has so many features" without the benefits. I also think a pretty good example is what Ty and Phillip did with ZPatterns. They had plenty of how-to implement in the API Documentation. It did take alittle while though, but thanks many times over for the learning experience it was fun. In other words half scientific facts(This is)/ half hocus pocus(Do This). >>2. One of the main points DC made at this years Python conference was >>that >>they have tried to focus the Zope core on too many audiences at >>once. Yes a problem. >>They >>had to have a clearer focus and chose developers as that focus. Of course they did. We're talking about "Core" services here. Like I said before once again I think it's the impletation part I'm stuck on. >>Of course >>I like this choice because I am a developer, but the more important >>point >>is that this tighter focus has the potential to make life easier for >>all of >>us. No just developers. You can call it what you want, but it is a tool that developers can use to get a job done. Content mangers and other network admin types about the API anyway. I imagine most if not all of zope users are progammers in some sense. >>Incremental restructuring of the Zope core and improved Zope >>developer >>documentation makes it much easier and more practical for DC and >>others to >>create layered Zope products that address other communities. Seems to be my point also. Perhaps I stepped in some fishpoo and need to learn how to get involved with the "Fishbowl" process. Thanks, Jimbo

1 0

using php on zope
by Stian Jenssen 08 Jun '01

08 Jun '01

> Hi there! > > I wan't to use php with zope, does anybody know how the header syntax > shall look like? > Tried diffrent syntaxes but i get wierd outputs, not as expected. >

3 2

Re: [Zope-dev] Bug in Zope VersionControl
by Martijn Pieters 08 Jun '01

08 Jun '01

On Fri, Jun 08, 2001 at 02:22:54PM +0200, Christian Theune wrote: > > > > I think we want to use: > > > > RESPOSE.setCookie(.... > > path=(REQUEST['SCRIPT_NAME'] or '/')) > > > > Could you file a bug in the Bug Collector at: > > > > http://classic.zope.org:8080/Collector > > > > Thanks! > > > > Thanks too, will do so. > There are too bugs already, one was mine, the other i don't know. Should > I really post a third? Please do. Refer to the other two bugs (2225 and 2234), but include my explanation (SCRIPT_NAME is '' in ZServer only setups, thus path is '', thus Opera ignores it). You can create a patch where you use the path=(REQUEST['SCRIPT_NAME'] or '/') code I proposed. Please say that I helped diagnose this, the core team'll contact me if they need more info. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------

1 0

Re: [Zope-dev] Bug in Zope VersionControl
by Martijn Pieters 08 Jun '01

08 Jun '01

On Fri, Jun 08, 2001 at 02:17:06PM +0200, Christian Theune wrote: > yes. we are right. Opera only sends the cookie in the version, but i couldn't > figure out, what zope is sending (using the tcpwatch proxy). so i don't know > what zope returns ... > the should be a line > > <== Cookie: ... > > or something I think, but there isn't. As soon as you press the 'join' button, Zope will send a 'Set-Cookie' header. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------

1 0

[mj@digicool.com: Re: [Zope-dev] Bug in Zope VersionControl]
by Martijn Pieters 08 Jun '01

08 Jun '01

(Could we please keep the list in the loop for both wider discussion and archiving?) On Fri, Jun 08, 2001 at 01:43:29PM +0200, Christian Theune wrote: > > REQUEST['SCRIPT_NAME'] is the root of the Zope server. In a pure ZServer > > environment, this is '/'. In a situation where the Zope server is running > > behind another webserver, and is not at the root of that server, > > SCRIPT_NAME represents the path to the Zope server. > > > > For instance, if your Zope server is presented to the outside world as > > 'http://a.server.com/a/path/to/zope/' then SCRIPT_NAME will be > > '/a/path/to/zope/', whereever you are in the Zope object hierarchy. > > > > Thus, a version cookie is bound to the root of the Zope server. In your > > case, it seems that Opera is ignoring the cookie path altogether, and > > instead falls back on the default, which is the path of the Version object > > itself. > > Okay. I have something for you. > > The REQUEST['SCRIPT_NAME'] is '' on my server. Could it be that - if zope > is on the root - it SHOULD be '/' but is ''? You are correct, SCRIPT_NAME is indeed '' in ZServer situations. However, see below. > Then per RFC it should be the location of the request (in this case > http://localhost:8080/asdf, where asdf is the version). The RFC is silent about this. Note that there are two specifications that may apply. One is the original Netscape specification, the other is RFC 2109: http://www.netscape.com/newsref/std/cookie_spec.html http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2109.html There is also a RFC2965 which defines a new 'Set-Cookie2' header with a new syntax. Neither RFC 2109 nor the Netscape spec specify what happens when a 'path=;' cookie is sent, they only specify what happens if the path attribute is absent. The fact that we set an empty path attribute is thus confusing and we should avoid this. > IE and Netscape poorely ignore the path, but Opera restricts the cookie > to the location of the Version. IE and Netscape have decided that in that case the server must have ment to say 'path=/;', while Opera chooses to interpret it the same way as an omitted path attribute. > Probably you want to check: > > if REQUEST['SCRIPT_NAME']=='': > REQUEST['SCRIPT_NAME']='/' > > wherever this variable is created ... > ??? I think we want to use: RESPOSE.setCookie(.... path=(REQUEST['SCRIPT_NAME'] or '/')) Could you file a bug in the Bug Collector at: http://classic.zope.org:8080/Collector Thanks! -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------

1 0

RE: Fwd: [Zope-dev] How to return downloadable content from Pytho n Method
by Blandford, Simon [BSS Audio UK] 08 Jun '01

08 Jun '01

Hi Gregor, > First off, please don't send HTML mail to the list. Ouch! Sorry! Easy mistake to make. > > You will have to set the Content-Type HTTP header to do that: > REQUEST.RESPONSE.setHeader('Content-Type', content_type) > where content_type is the right MIME type of the file you return, e.g. > something like 'application/msword' in your case. > Hope that helps. Yes it works! Thankyou for your help. Much appreciated, Simon B.

1 0