on 4/17/00 11:57 PM, Chris Meyer <[EMAIL PROTECTED]> wrote:
> This is definitely nice functionality [ImageServer].
Thanks! there is also a FileServer. The difference is essentially the
headers they set.
>> RunData is NOT global. Well, it is in the perspective of a single invocation
>> of Turbine, but it is unique across invocations. It isn't and should not be
>> cached or have stored as data ANYWHERE.
>
> I meant it in the sense of 'per invocation'.
Right. The purpose of RunData is to encapsulate the 'per invocation'
execution into one object to pass around. Since within the JVM I'm pretty
sure that just pointers are being made, I don't see this as a bad thing.
> It's good functionality, just a bit confusing to new users like me
> maybe. I think I'm starting to get it now...
>
> On a more pragmatic note:
>
> What do you think about changing the return types on Layout and Page like
> this?
>
> Assembler: New Method: Current Return: Proposed Return:
> ---------- --------------- --------------- ----------------
> Action performAction void void
> Layout buildLayout void ConcreteElement
> Navigation buildNavigation ConcreteElement ConcreteElement
> Page buildPage void ConcreteElement
> Screen buildScreen ConcreteElement ConcreteElement
You did a good job of explaining what you would change in the Proposed
Return, but not *why*.
> Also, 'buildAction' didn't sound right to me... so I put in 'performAction'.
I'm +1 on the name changes, just not the return changes until you give me a
reason why. :-)
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
