Re: [Zope3-dev] Indirection Reporter
On Fri, 2006-02-24 at 09:14 -0700, Shane Hathaway wrote: > Jim Fulton wrote: > > I think that such a tool would be useful. I see no benefit in trying to > > provide a through-the-web view. (Actually, I see a little benefit and > > lots of downside.) I recommend a simple command line tool instead that > > writes to standard output. > > What would be the downsides of a TTW view? Mainly that you'd have build the support for this into a running server, which seems like a bad idea to me. You'd need some funky mechanism for switching into and out of the tracing mode. I think there would be a lot more data that would be useful in a TTW interface. You may want to trace the publishing code. Overall, I think a simple command-line tool that creates a log would be a lot simpler, cleaner, and more useful. Jim ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Indirection Reporter
Jim Fulton wrote: I think that such a tool would be useful. I see no benefit in trying to provide a through-the-web view. (Actually, I see a little benefit and lots of downside.) I recommend a simple command line tool instead that writes to standard output. What would be the downsides of a TTW view? As Stephan commented, I suspect changes to the CA would be needed, although perhaps the machinery that Python's debugger uses could be leveraged somehow. A profiling hook would do it, but hopefully that's not necessary. Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Indirection Reporter
Shane Hathaway wrote: Here's another idea that occurred to me recently. I suspect this one needs no vote, but perhaps it should be done sooner than other ideas like the filesystem-based web root. Yes, I agree with the comments others have made and would certainly prefer to see this before a filesystem-based we root! cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Indirection Reporter
On Monday 13 February 2006 15:21, Shane Hathaway wrote: > > But my main question is: How will you be able to do this? :-) I could see > > a special hook into the adapter lookup. But then you would just get every > > adapter lookup sorted chronically. Will that be helpful? I think we would > > have to think very hard about what type of information is useful. If you > > have ideas, I would love to hear them. > > A simple chronological output might be enough for many cases. Showing > stack context might help. Filtering will probably provide for most > other needs. Users will normally use this with some question in mind, > like "what browser views is this page using?" To answer that question, > the user will probably filter the report to show only adaptation from > (any_object, IBrowserRequest). We'll need experience with the tool to > find out what filters are most useful. Then we'll provide a menu of > predefined filters. I would expect there to be many, many lookups. But maybe it is also a way to tell which lookups are done a lot. So, I would love to see an initial implementation that shows a simple list. I think this should be a quick thing. I think the difficulty will be in the filtering tools. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Indirection Reporter
On Mon, Feb 13, 2006 at 10:18:24AM -0700, Shane Hathaway wrote: > I want a way to inspect all of the indirections chosen in the course of > a web request or any other publishing operation. After executing a web > request, Zope will report all of the points where it made a decision > using the component architecture. It will show what decision it made > and which ZCML directive caused it to make that choice. I haven't the foggiest idea how that would be implemented, but if you could make it work, wow that would be cool. Both as a learning tool and as an invaluable debugging aid. -- Paul Winkler http://www.slinkp.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Indirection Reporter
Stephan Richter wrote: On Monday 13 February 2006 12:18, Shane Hathaway wrote: Thoughts? Will it work? Should it be a priority? I like the idea a lot and you could reuse quiet a bit of apidoc code to produce some nice output. But my main question is: How will you be able to do this? :-) I could see a special hook into the adapter lookup. But then you would just get every adapter lookup sorted chronically. Will that be helpful? I think we would have to think very hard about what type of information is useful. If you have ideas, I would love to hear them. A simple chronological output might be enough for many cases. Showing stack context might help. Filtering will probably provide for most other needs. Users will normally use this with some question in mind, like "what browser views is this page using?" To answer that question, the user will probably filter the report to show only adaptation from (any_object, IBrowserRequest). We'll need experience with the tool to find out what filters are most useful. Then we'll provide a menu of predefined filters. Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Indirection Reporter
On Monday 13 February 2006 12:18, Shane Hathaway wrote: > Thoughts? Will it work? Should it be a priority? I like the idea a lot and you could reuse quiet a bit of apidoc code to produce some nice output. But my main question is: How will you be able to do this? :-) I could see a special hook into the adapter lookup. But then you would just get every adapter lookup sorted chronically. Will that be helpful? I think we would have to think very hard about what type of information is useful. If you have ideas, I would love to hear them. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
