I've posted the source and binary of a prototype TCP Sampler - see bug 23398:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23398 I'll be continuing to develop it for use with our own private protocol (but I can't publish that code). This should help me find some of the faults in it, but I'm hoping to get some independent feedback on whether it is likely to prove generally useful, and what changes/enhancements are needed. As it stands, it can download a page from a web-server, and it seems to handle connection errors OK. I still need to do work in the following areas: - ensure the testStarted() etc methods are called in the handler(s) (in case needed) - Specify protocol handler name via GUI (perhaps) - Create an (abstract) TCP Client class that protocol handlers can extend ++ this should provide default read/write methods, including looking for message terminator(s). ++ and a way to specify when to disconnect. At present, disconnect is only done at end of test - add its new resources to messages.properties - add some optional parameters to the GUI - tidy up the GUI Our private protocol does not have a specific login stage, so I've not implemented this - but the fields are still in the GUI. [Patrick - does your protocol need to login? and logout?] -- Sebastian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
