[Seaside] Re: [Seaside-commits] aubergines/seaside Seaside2.mc,1.14,1.15

[Stephen Pair]

Nevin Pratt wrote:

> Comanche won't log Seaside component accesses.  It can only log URL's. 
> And Seaside's URL's aren't particularly meaningful in a log.
>
> If a subclass of WAKom can figure out what Seaside component(s) is/are 
> being accessed when it sees a given Seaside URL, then I think Comanche 
> logging can do it all.  Otherwise, Seaside must do the logging.
>
> And if Seaside is doing the logging, there is a bunch of stuff in the 
> Comanche HttpRequest that it needs.
>
> And off hand, I don't see a way for the WAKom subclass to know the 
> components (and subcomponents) that are being accessed via a given 
> URL. Seaside is just too dynamic for that.  After all, it's not hard 
> to have a given component hot swap another component on the fly.  Just 
> set an instance variable in the Seaside component to contain a 
> subcomponent that it wants rendered for that access.  How in the world 
> could Comanche possibly know it did that?
>
> Thus, I lean towards giving Seaside more HttpRequest knowledge.

Well maybe not.  If Seaside had an interface allowed you visit the WAComponent tree for a given WARequest, you could use that to visit the tree and generate whatever log information you wanted.

- Stephen