From: Chris W. <ch...@cw...> - 2001-12-29 22:18:26
|
On Fri, 2001-12-28 at 17:10, And...@Be... wrote: > - Devel::DProf works OK with OI in "script mode". Just use it like the docs > say: perl -dDProf thescript.pl and then: dprofpp I used this with some > userlisting scripts etc. Cool -- I'll have to play around with this in the next n months, when I get some free time :-) > - actions and base_page: > If you abstract this, then all we to is map some partial url to some code. > The action table does this directly by mapping say /news to > mysite::Handler::News. base_page does little different things now, map e.g. > /stats/mistot.xls to a db query ( storage type database ) or /index.html to > a file handler (storage filesystem ) and since the last version > /family_pics/ to again code to display a directory. Why not have /news be a > base_page with type handler and point to the right code? How could this be > done? Maybe oi_manage could create the necessary base_page objects. If we > had this, the conductor only needed to look at one place to find the handler > to call. I am definetly not sure, if this is a good idea - just thinking > loud. This is something to think about. But the main difference I see is that a normal action (e.g., '/news') says to OpenInteract that it defines tasks within that entire URL-space -- every URL beginning with '/news' should just be passed to that handler which will deal with generating the content. Directory handlers instead only hook into a single URL rather than entire URL-space, and they can be inherited and used across other URLs as well. So '/mynews/' might be handled by a directory handler but '/mynews/latest.html' is a normal page which the directory handler never has to deal with. As my wife is fond of saying, this may be a distinction without a difference. And I may be too close to tell right now -- we might need to let this ferment a little to see what it smells like :-) Later, Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |