<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73">
<TITLE>RE: [Seaside] Re: Distributing other than HTML content</TITLE>
</HEAD>
<BODY>
<BR>
<BR>
<P><FONT SIZE=2>> Sam> I need to distribute dynamically generated binary content</FONT>
<BR><FONT SIZE=2>> Sam> (presented as a MIME document) directly from Seaside, without</FONT>
<BR><FONT SIZE=2>> Sam> going through an HTML page first and through a link.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I've done it but it's not very clean:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> renderContentOn: html</FONT>
<BR><FONT SIZE=2>> self feed refreshFeed.</FONT>
<BR><FONT SIZE=2>> self session returnResponse:</FONT>
<BR><FONT SIZE=2>> (WAResponse new</FONT>
<BR><FONT SIZE=2>> contentType: 'text/xml';</FONT>
<BR><FONT SIZE=2>> nextPutAll: self feed asXML;</FONT>
<BR><FONT SIZE=2>> yourself)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Is there a better place to do this?</FONT>
</P>
<P><FONT SIZE=2>We are serving wsdl files using WATask subclasses</FONT>
<BR><FONT SIZE=2>with a logic similar to yours in the #go method.</FONT>
</P>
<P><FONT SIZE=2>That works fine provided that the web service client</FONT>
<BR><FONT SIZE=2>deals properly with Seaside HTTP redirections.</FONT>
</P>
<P><FONT SIZE=2>Michel.</FONT>
</P>
<BR>
<P><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Sam</FONT>
</P>
</BODY>
</HTML>