Resource references vs serving resources through web server

[Alec Swan <al...@gmail.com>]

Hello,

I am wondering if there is a significant performance overhead of using
resource references vs serving those resources through a web server,
e.g. Apache, which is fronting the servlet container running Wicket
app?

What advantages do resource references have over just hard-coding
resource paths?

Thanks,

Alec

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Resource references vs serving resources through web server

[Igor Vaynberg <ig...@gmail.com>]

some resources are shipped in jars, so unless you manually unpack the
jars there is no way apache can serve them. what you can have apache
do is cache them after they have been served once.

performance-wise there should be minimal overhead.

-igor


On Thu, Sep 1, 2011 at 2:03 PM, Alec Swan <al...@gmail.com> wrote:
> Hello,
>
> I am wondering if there is a significant performance overhead of using
> resource references vs serving those resources through a web server,
> e.g. Apache, which is fronting the servlet container running Wicket
> app?
>
> What advantages do resource references have over just hard-coding
> resource paths?
>
> Thanks,
>
> Alec
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org