[Seaside] Seaside Login and so on

[Julian Fitzell]

Giovanni Giorgi wrote:
> Hi Julian!
> 
> On Martedì, ago 5, 2003, at 20:11 Europe/Rome, Julian Fitzell wrote:
> 
>> [...]
>> Hi Giovanni,
>>
>> First off, I'm not quite sure what you mean about directly invoking a 
>> component: you can only enter a seaside application via a defined 
>> entry point - so unless you have an entry point for that component 
>> nobody will be able to enter it directly.
> 
> I am used to use something like:
> 
> MasterWAComponent>>renderContentOn: html
>     session heLikesSqueak ifTrue:[
>               self call (CalledWAComponent new)
>     ]
> 
> I'd like to avoid session checking in every renderOn (I have a lot of 
> renderOn: .... :)
> Perhaps I should avoid using  the call:/answer: syntax?

Yeah, I don't think you should be using #call: in a render method (I'm 
not exactly sure what the consequences are but I can't think of any 
reason you would need to).  In that case you want to do:

self render: CalledWAComponent new.

You only want to use #call: and #answer: during the action phase (when a 
user does something), not during the rendering phase.

Julian