I have to agree with Filip and I'll state it a bit more strongly: if you are using onActivate for access control your app will suffer from significant maintenance issues that will only get worse and more complex with each page you add, and even nastier if your access control logic's requirements evolve. If your app is small, ok, but if not you should reconsider your approach sooner rather than later.
chris maxthesecond wrote: > Well, in my case when I have two or more onActivate handlers I've seen all > them called one after the other wich of course is not what I expect ,besides > the fact of having just one onActivate frees you of having to check common > isues like for example loggin , or administrative rights in many places. > -- http://thegodcode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
