Technical Limit on Mount Points

[Arjun Dhar <dh...@yahoo.com>]

Hi,
 I fave a ton of possible dynamic content where for each content I have to
associate a Mount Point.
im thinking of a strategy to do that efficiently.

To cater to it, following questions:
1). What decides the technical limit to the number of Mount points possible?
(Does it load all the mount points into memory, or applies some sort of
caching that can use persistence if required)?

Example usage per mount point: application.mount(new
MixedParamUrlCodingStrategy(myPageX, pageTemplateClass, new
String[]{"pageId"}));

2). Would a considerable number of Mount points degrade performance? 

thanks

-----
Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing!
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Technical-Limit-on-Mount-Points-tp3699113p3699113.html
Sent from the Users forum mailing list archive at Nabble.com.

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

Re: Technical Limit on Mount Points

[Arjun Dhar <dh...@yahoo.com>]

On my own investigation :-
WebRequestCodingStrategy$MountsMap :

		/** backing map */
		private final TreeMap<String, IRequestTargetUrlCodingStrategy> map;

... that decides the data structure for the mounts, imo/

-----
Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing!
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Technical-Limit-on-Mount-Points-tp3699113p3700408.html
Sent from the Users forum mailing list archive at Nabble.com.

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