1 May
2006
1 May
'06
8:14 p.m.
Hi,
Yes, this is clear (because decorators are part of model) if looking
at "Seaside only" solutions. My statement above was made by thinking
Seaside/Pier itself as a view in a greater solution. But ok, where to
draw the borders between model and view may be somewhat academic :-)
Hope this clarifies some things,
Oh, I understand the implementation in Pier, and also the intention.
I only want to play with a different point of view ;-)
- if one say model or buisness logic, one could
easily think at the
multi tier architectures. Here it is a common way to say, security
must handled be the database objects (for example), not by the
objects which are only a viewer. My problem is 1) that these viewers
are mediators of security and 2) that in complex systems this
viewers can be itself complex object with model-view architecture.
In Pier the security is not handled by the view, but by the model.
That is also the reason why it works in the Seaside view and in the
OmniBrowser view without additional code.
Side-note: I do not claim that the security model of Pier is secure
and impossible to break, as with everything I write as open-source it
suits my personal needs. Bug-reports, fixes and enhancements are
always welcome.
Hey ! Don't be angry, I know the rules of open-source, and I never
want to be destructive. I'm only interested in different point of
views, discussions and the question "why ?" 8-) So thank you very
much for the answers. I hope we could talk a little bit further at
some SqueakNic or something like this :-)
Greetings
Hans