[Seaside] jQuery serialize proxy issue
renggli at gmail.com
Sun Aug 28 09:34:41 UTC 2011
For Seaside it doesn't matter much if there is a GET or POST request,
but if you are calling external services or are using Seaside-REST it
might make a big difference. I think it would be wrong to try to
change the request type behind the back of the user. It would be
possible to change the default request type in Seaside, but then it
would be different to the default GET that JQuery clearly documents
(http://api.jquery.com/jQuery.ajax). I suggest not to change it.
On 27 August 2011 17:08, Adriaan van Os <a3aan at xs4all.nl> wrote:
> Some proxies do not allow (very) long urls in an HTTP GET. This means that
> JQAjax>serialize: won't work. It requires you to make it an HTTP POST.
> Like this
> serialize: aQuery
> "Serialize the elements matching aQuery and evaluates the associated
> self class = JQAjax ifTrue: [self type: 'POST'].
> self enableCallbacks.
> self addParameter: aQuery serialize
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside