Paul McMahan wrote:
You raise a good point and it sounds like the idea would work, but I'm
concerned it could lead to a proliferation of dojo webapp components,
one for each custom configuration. I wonder if it might be possible
to instead create a servlet in the current dojo app that could build
and cache custom configurations on the fly. That way we could keep
the current standard library in place for unoptimized dojo apps but
still serve up customized configurations from this same location for
optimized dojo apps.
Off the top of my head, invoking the servlet could look something like:
/dojo/dojo?widget1=tree&widget2=table&...
This approach also keeps us in line with some of the other motivations
for making dojo a native component in the server -- easy to upgrade,
easy to reference from deployment plans, keeps the server footprint to
a minimum, etc.
Best wishes,
Paul
On 10/5/06, Jay D. McHugh <[EMAIL PROTECTED]> wrote:
Hello all,
I finally managed to get my project development/testing server up and
working on 1.2-snapshot (Thanks again djencks!).
And I finally got to see the JMX console that was added - Which is very
cool.
But, I think that it brings to light a performance issue. Because we
are using dojo widgets that are not 'bundled' into the dojo.js library,
we end up pulling down -many- individual files to support the widgets.
I think we should consider building our own dojo bundle (I'm going to
start looking into exactly how to do this) and deploying it to something
like /geronimo-dojo and using that for console apps. Pulling the one
(slightly larger) library -should- increase response time since we won't
need all of the extra file requests/responses going over the wire.
I do like having dojo deployed to /dojo built into the server though and
would like to keep the base library there (so far I have just been using
the AJAX portion of dojo in my own apps - so I haven't needed any
widgets).
Does anyone have any thoughts about this?
Jay
Hey Paul,
That sounds like it would be a very cool servlet.
Right now, trying to figure out the logistics of making it work are
tying my brain into knots.
I will see if I can figure out a way to do it though.
(suggestions welcome though).
I'll let you all know if I come up with something.
Jay