I see them being returned with 304 not-modified status code
(using friendly urls, but this shouldnt matter)
On Tue, Jul 15, 2008 at 6:00 AM, Jeremy F. Kassis
<[EMAIL PROTECTED]> wrote:
>
> Hmm. Just finished upgrade to 4.1.5 and the asset service clearly isn't
> caching dojo .js resources.
>
> Usi
Hmm. Just finished upgrade to 4.1.5 and the asset service clearly isn't
caching dojo .js resources.
Using firebug, I can see every request. There is no MD5 digest in any of the
urls, and when I add a breakpoint to the asset service and step through the
service() method, I can see it open the reso
You could try upgrading to a current release - 4.1.5 looks to be your
best bet right now.
http://tapestry.apache.org/download.html
It handles all the caching stuff / reduced dojo footprint / other
things already. I would definitely take the time
to attempt an upgrade to 4.1.5 first if I were pu
I know this is an old thread, but I've been working on a T4.1.1 application
for a long time and it's about to go live. Our recent live site testing
shows that these huge .js files kill the initial page load and they aren't
really getting cached by the browser, so they transfer on *every* page load
I know this is an old thread, but I've been working on a T4.1.1 application
for a long time and it's about to go live. Our recent live site testing
shows that these huge .js files kill the initial page load and they aren't
really getting cached by the browser, so they transfer on *every* page load
Jesse Kuhnert gmail.com> writes:
>
> Just as an update on this thread, it looks like they've been working on
> build size and I'm currently able to create a 23kb file for dojo..So, I hope
> that will speed things up a little bit.
>
Great, what a progress!
Reducing the size of the "dojo.js" is
Hi Jesse,
23Kb? The original 176Kb shrinked to 176Kb with the same features? I'm
stunned! :-)
That will sure speed thinhs up a bit!
Regards,
On 8/13/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Just as an update on this thread, it looks like they've been working on
build size and I'm currentl
Just as an update on this thread, it looks like they've been working on
build size and I'm currently able to create a 23kb file for dojo..So, I hope
that will speed things up a little bit.
On 8/5/06, Beat Hoermann <[EMAIL PROTECTED]> wrote:
Jesse Kuhnert gmail.com> writes:
> You should find t
It's more for "javascript" in general now. As I've stated before though,
nothing is set in stone yet wrt how dojo is included. It sounds already like
I'll need to investigate a few paths to find the most optimal solution to
fit all needs.
On 8/7/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
I thin
I think the Tap devs decided to stop maintaining custom validation logic and
offload that on a 3rd party lib: dojo. I believe that's why you're seeing
dojo included when you have forms. It might be possible to tweak Tapestry so
that it doesn't include dojo if the form doesn't have any validation d
I haven't invesitgated 4.1, but surely you can always replace the
default 170KB dojo.js with a stripped down one, since dojo provides
the possibility of custom builds. If you actually use the dojo
functionality, of course, your code will be downloaded piecemeal by
dojo, but if you avoid the using
Jesse Kuhnert gmail.com> writes:
> You should find that no XmlHttpObject's will be created against your will
> unless you specifically set a parameter or call a method that is designed to
> do it. (whether directly or as a side effect).
Good idea!
> The framework does continue to include javasc
Bernard man.poznan.pl> writes:
>
> Beat Hoermann wrote:
> > I surrounded the form component with a shell component. After all, my tiny
web-
> > app, just displaying a simple text field and a submit button, not using
ajax
> > nor any dojo things, was forced to load the 173 KByte heavy "dojo.js
Yes, it was a mistake to leave that parameter in there at all. It was during
a fanciful/fleeting moment where I thought it would be a good/practical idea
to globally turn "ajax" on/off like a water spicket.
Rational thought soon returned when actually implementing these features.
You should find
I think the intention is that ajax functionality is disabled by default.
"Bernard" <[EMAIL PROTECTED]> skrev i en meddelelse
news:[EMAIL PROTECTED]
> Beat Hoermann wrote:
>> I surrounded the form component with a shell component. After all, my
>> tiny web-
>> app, just displaying a simple text f
Beat Hoermann wrote:
I surrounded the form component with a shell component. After all, my tiny web-
app, just displaying a simple text field and a submit button, not using ajax
nor any dojo things, was forced to load the 173 KByte heavy "dojo.js". The
integration of dojo into Tapestry seems qu
I created a form with a single text field. To my surprise Tapestry 4.1
rendered an HTML-page that contained a piece of javascript with dojo-commands.
Since the "dojo.js" was not loaded into the HTML-page it gave me an error. So
I surrounded the form component with a shell component. After all, m
17 matches
Mail list logo
