You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Bastian Voigt <po...@bastian-voigt.de> on 2007/04/17 18:58:25 UTC
Tapestry Bug 961: Large XTile responses cut off after 4096 bytes
Hi,
I have a question regarding bug #961. Jesse said the bug won't be fixed in
tapestry because the "client side XHR" api can be used as an alternative.
I did not really understand this comment, since with XTile in version 4.0.3 it
is not possible to use this client side XHR api. Rather, the XTile component
itself needs to be modified to use this XHR api, if I'm not completely
mistaken.
So how can I get around this bug?
Thanks
Bastian
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon 040/67957171
mobil 0179/4826359
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Please read this: Tapestry Bug 961 Large XTile responses cut off
Posted by Bastian Voigt <po...@bastian-voigt.de>.
Hi *,
please someone have a look into this. The JIRA Bugreport is here:
http://issues.apache.org/jira/browse/TAPESTRY-961
On Tuesday 17 April 2007 18:58, Bastian Voigt wrote:
> Hi,
> I have a question regarding bug #961. Jesse said the bug won't be fixed in
> tapestry because the "client side XHR" api can be used as an alternative.
>
> I did not really understand this comment, since with XTile in version 4.0.3
> it is not possible to use this client side XHR api. Rather, the XTile
> component itself needs to be modified to use this XHR api, if I'm not
> completely mistaken.
>
> So how can I get around this bug?
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon 040/67957171
mobil 0179/4826359
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org