[Seaside] Seaside to return (only) xml data?

[Jay Hardesty]

OK - now I see:  the #handleRequest: method in
WARequestHandler would be the one overridden in
a subclass of WAEntryPoint.

Would I there replicate the cookie-checking that exists
in WAApplication>>handleRequest:  in order to route
requests from particular users to particular objects
(maintain sessions)?

Thanks once more,
Jay



On Jun 5, 2007, at 8:38 PM, Jay Hardesty wrote:

>
> Thanks for the response.  I see #handleRequest: in WAApplication,
> but not WAEntryPoint - is that the place?
>
> Does this chunk of code in #handleRequest: maintain the connection
> between particular users and particular object instances (as happens
> transparently when using WAComponent)?
>
> 	self useSessionCookie ifTrue:
> 		[aRequest cookies at: self name ifPresent:
> 			[:v |
> 			aRequest fields at: self handlerField ifAbsentPut: [v]]].
>
> Thanks again,
> Jay
>
>
>
> On Jun 5, 2007, at 8:02 PM, Avi Bryant wrote:
>
>> On 6/5/07, Jay Hardesty <jayh at panix.com> wrote:
>>
>>> So I assume that my renderContentOn: method
>>> should contain something like:
>>>
>>>         self session returnResponse: (WAResponse new
>>>                 contentType: 'text/xml';
>>>                 nextPutAll:  (some xml formatted string here...);
>>>                 yourself)
>>
>> Code's right, placement's wrong - you shouldn't use #returnResponse:
>> from within a #renderContentOn: , use it from within a callback.
>>
>> If your application is purely XML based, I wouldn't use WASession or
>> WAComponent at all, but just subclass WAEntryPoint and override
>> #handleRequest:.
>>
>> Avi
>> _______________________________________________
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside