DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11419>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11419 allow values to be stored and accessed during run and enhance performance Summary: allow values to be stored and accessed during run and enhance performance Product: JMeter Version: Nightly (Please specify date) Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Main AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Web sites often lead users down side paths (such as via opening a new temporary browser window), and then bring the user back to the main path. JMeter has no notion of such side paths, and everything is strictly linear. However, frequently, JMeter needs the next request to access values that were present 3 or 4 requests ago (this is referring to Response-Based modifiers and parsers). Thus, I'd like JMeter to be able to grab those values when they are available, and then store them and allow requests down the line to re-use those values. Functions and modifiers should be given access to a central location (each thread holds separate values though) where such values can be named and stored. This should allow one function to store it's values and obviate the need to have multiple instances of that function in various different parameters and fields, which should increase performance. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
