on 7/12/2000 7:00 AM, "Regis Koenig" <[EMAIL PROTECTED]> wrote:
>> Yes it is possible - and in fact I want to do exactly this too. The plan
>> I have is to have a special Screen subclass (FlashScreen) from which all
>> my screen classes that need to generate text for flash get derived. Then
>> I derive from DefaultPage and check to see if the screen is a
>> FlashScreen - if it is then the screen is invoked directly bypassing
>> layouts/navigations, otherwise the superclass stuff gets invoked (all
>> the HTML preparation).
>
> I've had a closer look on how the core Turbine servlet works, and it
> seems that the all is there :-). The Turbine engine look in the RunData
> for 2 methods isPageSet() and isOutSet(). If the user has called
> getOut() in its Screen, isPageSet() is set to false, and outSet is set
> to true, and the layout output is ignored. If, screen.getLayout()
> returns null, the Layout stuff is not executed (by the DefaultPage), and
> outSet remains false. So, there is no work needed in the core :-)
>
> Anyway, the RunData.getOut() method returns a PrintWriter which is
> unusable for writing raw binary data. On top of that, the mechanism for
> writing Screens for arbitrary type is not intuitive today. So I want to:
Regis,
What are you talking about? Have you looked at the ImageServer screen? It
returns binary data just fine. I did that Screen as a perfect example of how
you can return binary data through a screen without any problems.
I vote -1 to any changes that you are proposing since this stuff is already
working just fine. Tell me if I am confused.
thanks,
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
