Session Management Performance

[Ben Sullivan]

Hi
I am studying for my SCWCD exam and was wondering if there was any way around the performance problems introduced by URL rewriting?
Thanks
Ben

[Stepan Samarin]

Ben, you say that URL rewriting introduces performance problems. Personally, I don't see any bottleneck in this alternative to cookies. Can you please tell us your vision, may be some facts.

[Peter den Haan]

I wouldn't say that there are any serious performance implication to URL rewriting -- because most of the time, you don't. If the client supports cookies (which will be 99% of the time) then HttpServletResponse.encodeURL() will return your url String unchanged, with no object creation and little overhead.
- Peter

[Ilja Preuss]

Originally posted by Peter den Haan:
I wouldn't say that there are any serious performance implication to URL rewriting -- because most of the time, you don't.

Even if you actually do, why would there be a serious performance hit?

[Peter den Haan]

You're right, there probably isn't, unless you have a lot of URLs on your pages; I guess that could give a fair bit of object churn.
- Peter

[Jack Shirazi]

The design doesn't have any inherent bottleneck. I've learned through years of experience not to anticipate implementation bottlenecks. You usually anticipate the wrong one.
There are always situations where almost anything can become a bottleneck depending on the implementation, the load and the configuration.
--Jack Shirazi
JavaPerformanceTuning.com