- Zope - Zope lists

Re: [Zope] sqltest vx. var
by Jeffrey P Shell 10 Apr '99

10 Apr '99

>From: Philip Aylesworth <zopelist(a)regalint.com> > I'll correct myself here. I was thinking of the  tag. I > don't know what  does that  or >  won't do... A _very very_ nice feature of #sqltest is the 'multiple' feature. For example: SELECT * FROM inbox WHERE  If doc_status is passed in as a single value, like "foo", the SQL statement will be rendered as:: SELECT * FROM inbox WHERE doc_status='foo' BUT!!! (this is where it gets good), if doc_status is passed in as a list/sequence, like ["foo", "bar", "drop", "ship"], it will be rendered as:: SELECT * FROM inbox WHERE doc_status in ('foo','bar,'drop','ship') This is an _extremely_ handy feature of #sqltest. Prior to #sqltest, doing the above might be like: SELECT * FROM inbox WHERE doc_status in (  '' , ) (#else used to be used where #unless is used today). The above code also always required doc_status to be passed in as a sequence. #sqltest is smart enough (I believe - i've never been bitten by this) to detect the difference between strings and lists. I've used #sqltest with multiple many times with Acquisition where a folder property would define part of a SQL statement. That property in some cases would be a single value, in other places it would be a tokens or lines property. So, in otherwords, you get the type checking, the multiple, the optional, etc... with #sqltest that you don't get otherwise. About the only problem is that #sqltest currently doesn't do not-equals or "not in (...)". .jPS | jeffrey(a)digicool.com zope, through the web. www.zope.org

3 2

Re: [Zope] "dtml_source"
by Tony McDonald 10 Apr '99

10 Apr '99

> Someone posted an External Method to display DTML Document source recently. > I've modified it to interpret paths, so now one can say: > http://www.zope.org/dtml_source?path=/x/y/z > and it will show the source of z, an object inside y, which is an object inside x. > And so on. Maybe there's a reason the original didn't do this? > > Anyway, here's my version of Extensions/dtml_source.py :- > > import string > def view_source(self, path): > "View the source of a Document" > for id in string.split(path, '/'): > if not id: > continue # Leading / > if id not in self.objectIds(): > id = None > break > # Walk down object hierarchy > self = getattr(self, id) > if not id: > self = getattr(self, 'index_html') > return self.read_raw() > I think that the confusion over dtml_source is due to its 'zopish' behaviour ... :) Using the 'old' dtml_source, urls such as server.org/dtml_source?path=/ninja/turtle/index_html only gets you the source of the top level index_html This is the way you would type in the URL to a non-zope system (ie the dtml_source 'lives' at the top level of the 'directory' and so everything is 'underneath' it) However, if you try the url server.org/ninja/turtle/dtml_source?path=index_html you get the source of the index_html at the level of 'turtle'. A *huge* lightbulb went on when I tried this. This is the 'zopish' way and uses acquisition to get the job done, ie dtml_source is 'called' at the level of turtle, which doesn't find it and passes it up to ninja who also passes it to the top level ('/' in unix parlance) who can process the request because it finds dtml_source at its level in the heirarchy. hope this helps, tone.

1 0

"dtml_source"
by piers＠cs.su.oz.au 10 Apr '99

10 Apr '99

Someone posted an External Method to display DTML Document source recently. I've modified it to interpret paths, so now one can say: http://www.zope.org/dtml_source?path=/x/y/z and it will show the source of z, an object inside y, which is an object inside x. And so on. Maybe there's a reason the original didn't do this? Anyway, here's my version of Extensions/dtml_source.py :- import string def view_source(self, path): "View the source of a Document" for id in string.split(path, '/'): if not id: continue # Leading / if id not in self.objectIds(): id = None break # Walk down object hierarchy self = getattr(self, id) if not id: self = getattr(self, 'index_html') return self.read_raw()

1 0

Zope to plain html
by Tom Deprez 10 Apr '99

10 Apr '99

Hi all, I'm willing to make my site in Zope. I see several benefits from it. And I will use it at my own server... but, unfortunately, our hospital wants to place some pages also on another server.... and yes.... they don't want to use Zope... :-(((. So is it possible... To convert my Zope pages to some plain html files? e.g. a page which inherits the header and footer of a parent folder --> in webpage they will be combined to one page... Is this possible? It will help me a lot. Then I can continue to design my pages in Zope. And later on, confice other webservers to use Zope. But until then I can give them plain easy html-pages.... Thanks in advance, Tom.

6 6

RE: [Zope] How to get the DTML code from a document/method?
by Rob Page 10 Apr '99

10 Apr '99

<SNIP> > > (this was from trying /dtml_source?path=index_html but path='anything > else' gives the same error). What about http://server.org/dtml_source?path=/index_html The leading slash is significant by virtue of the split in the source. > Is there a reason why there are two return statements in the external > method, when it seems that only the return doc.read_raw() is going to > be called? Yeah -- because slacker Rob didn't read before clicking send. Chris Petrilli also noted this. The second return in, um, optional. :^) --Rob

3 2

Re: [Zope] Has anyone tried authentication accross multiple servers?
by Phillip J. Eby 10 Apr '99

10 Apr '99

At 11:29 AM 4/8/99 +1000, Jay, Dylan wrote: >I need this for a website I'm setting up so that users can download from >several different locations around the world. I don't want users to have to >type in their password twice. I presume there is no way to do this via basic >authentication which leaves cookies. Has anyone tried this? > I'm in the midst of figuring out how to do authentication with cookies. The only way I can see to get ZPublisher to work intelligently with cookies is to hack the "unauthorized" method of the ModulePublisher class so that a login page can be called. One caveat for your project: cookies will only work across servers if the servers share a common domain, e.g.: foo.bar.com and baz.bar.com.

2 1

RE: [Zope] access to zope.com ? a bad router
by Ken Manheimer 09 Apr '99

09 Apr '99

On Friday, April 09, Scott Robertson sroberts(a)codeit.com wrote: > > I just ran a traceroute from here to zope.org and got pretty reasonable > > response times. Now if I try for "zope.com", that's a different story.... > > That's interesting two different DNS servers say zope.com is > 206.156.192.139, shouldn't it be 209.67.167.110 ??? Looks like the registered DNS stuff (NIC,etc) for the other zope domains have to be revised - the right guys been notified. For now, though, the thing to do is to not do that:-) (Ie, go to zope.org, not .com or .net...) Ken Manheimer klm(a)digicool.com

1 0

access to zope.com ? a bad router
by Robert OConnor 09 Apr '99

09 Apr '99

Again today I couldn't access the zope.com website. The trace reveled: 1 1184 ms 109 ms 105 ms stan-m010.cybertours.com [208.153.18.2] 2 110 ms 110 ms 110 ms stan-r1.pivot.net [206.98.61.126] 3 115 ms 115 ms 109 ms prtl-r0-e3-0.cyberTours.com [206.98.60.253] 4 120 ms 120 ms 114 ms borderx1-hssi4-0.Boston.cw.net [204.70.179.109] 5 125 ms 129 ms 119 ms core-fddi-0.Boston.cw.net [204.70.2.33] 6 125 ms 120 ms * core4.WestOrange.cw.net [204.70.4.77] 7 129 ms 124 ms 125 ms sprint3-nap.WestOrange.cw.net [204.70.10.226] 8 * 125 ms 119 ms pnnj-01.core.exodus.net [192.157.69.25] 9 * * 135 ms dcr01-h10-0-0.jrcy01.exodus.net [209.1.169.209] 10 135 ms 130 ms 127 ms bbr01-p1-3.jrcy01.exodus.net [216.32.173.122] 11 130 ms 135 ms 131 ms bbr01-p5-0.hrnd01.exodus.net [209.185.249.214] 12 140 ms 124 ms 134 ms bbr02-p6-0.hrnd01.exodus.net [209.185.249.2] 13 220 ms 204 ms 205 ms bbr02-p0-1.irvn01.exodus.net [209.185.9.206] 14 205 ms 204 ms 205 ms dcr02-p0-0-0.irvn01.exodus.net [209.185.249.9] 15 210 ms 205 ms * rsm-ir-b-vl920.lan.exodus.net [209.67.128.102] 16 269 ms * * zope.org [209.67.167.110] 17 204 ms 205 ms * zope.org [209.67.167.110] 18 * 205 ms 204 ms zope.org [209.67.167.110] Is there a problem with an exodus.net router. Is exodus.net the zope ultimate provider? This is the third time this week. -bobo connor bob(a)rocnet.com

3 2

Re: [Zope] access to zope.com ? a bad router
by Bill Randle 09 Apr '99

09 Apr '99

I just ran a traceroute from here to zope.org and got pretty reasonable response times. Now if I try for "zope.com", that's a different story.... Here's the traceroute: saab# traceroute zope.org traceroute to zope.org (209.67.167.110), 30 hops max, 40 byte packets 1 flamebait.coinet.com (192.168.100.1) 7 ms 2 ms 1 ms 2 ns.coinet.com (204.245.234.8) 3 ms 3 ms 2 ms 3 gw-mtj.mtjeff.com (204.119.16.254) 37 ms 19 ms 39 ms 4 s5-3-1.pdx10.or.nw.verio.net (199.2.96.193) 76 ms 35 ms 31 ms 5 fe4-0-0.pdx0.verio.net (129.250.30.129) 24 ms 41 ms 57 ms 6 pdx0.smf1.verio.net (129.250.3.21) 110 ms 60 ms 71 ms 7 smf1.smf0.verio.net (129.250.3.17) 77 ms 74 ms 44 ms 8 smf0.pao5.verio.net (129.250.3.13) 75 ms 77 ms 41 ms 9 ibr01-p6-0-0.sntc02.exodus.net (209.1.169.81) 51 ms 69 ms 76 ms 10 209.185.9.210 (209.185.9.210) 39 ms 43 ms 59 ms 11 bbr02-p1-1.sntc03.exodus.net (209.185.9.49) 64 ms 75 ms 53 ms 12 bbr02-p2-0.sntc02.exodus.net (209.185.249.145) 60 ms 107 ms 57 ms 13 bbr01-p6-0.sntc02.exodus.net (209.1.169.241) 71 ms 72 ms 75 ms 14 bbr01-p5-0.irvn01.exodus.net (209.185.249.218) 83 ms 113 ms 55 ms 15 dcr02-p6-0-0.irvn01.exodus.net (209.185.249.21) 65 ms 52 ms 53 ms 16 rsm-ir-b-vl920.lan.exodus.net (209.67.128.102) 112 ms 124 ms 67 ms 17 www.zope.org (209.67.167.110) 52 ms 60 ms 84 ms -Bill Randle Central Oregon Internet billr(a)coinet.com

2 1

RE: [Zope] access to zope.com ? a bad router
by Michel Pelletier 09 Apr '99

09 Apr '99

> -----Original Message----- > From: Scott Robertson [mailto:sroberts@codeit.com] > Sent: Friday, April 09, 1999 12:39 PM > To: Robert OConnor > Cc: zope(a)zope.org; support(a)codeit.com; traceroute(a)codeit.com > Subject: Re: [Zope] access to zope.com ? a bad router > > > > > Exodus claims that they are aware of the problem and our in > the process of > upgrading the bandwidth to their various peering points. Same > old story. > They've requested that I send them traceroutes from the troubled > connections. I figured we could have some fun with this, if > the zope list > is willing to help. If anybody thinks that the zope.org is > running slow > could you please e-mail a traceroute to traceroute(a)codeit.com. > > Thanks in advance for your help! > > Hmm.. the thing is traceroutes are just so useless for this kind of evaluation. IMO, the best method for determining where the fault lay are two mtrs, one from the source to the destination and vice versa (mtr is a program that runs a traceoute, and then continuously pings each router along the route giving you a real time packet loss figure). Traceroutes are just slices of the problem, and without capturing both sides of the link over a period of time they can be interpreted to mean just about anything. I think Exodus is stalling on you. My guess is they're going to take all your traceroutes and process them right into /dev/null. But perhaps the effort will stir some action there. Sorry to sound like a defeatest, but I have some bad memories dealing with any and all NSPs. -Michel > > >

2 1