Hi, The JRun 3.1 release note says: > Tag handlers are cached per instance per page. For example, if a JSP > calls the same custom tag twice, JRun caches two instances. > If your tag handler performs any kind of state management, you will > have to implement the Tag.release method to perform clean up before > JRun caches the tag instance. That's great, but we're wondering how concurrent, multi-threaded access to the same page (and thus to the same tag instance) is solved? Aren't the tag setters from the different threads going to (potentially) interfere? Thanks, -- Oliver ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
