Jeremy Arnold wrote:
[...] But since most threads are sleeping most
of the time, perhaps we can come up with some sort of thread pool, so
that a large number of JMeter threads (perhaps better to call them
users in this case) could be handled by a smaller number of JVM
threads. It could be
Jeremy Arnold wrote:
Mike,
Jordi did all the work -- I just spent 5 minutes having Eclipse look
for where methods were called from.
Yeah, but I was pretty lost.
Getting a dump of CVS sounds like a reasonable plan for this
release.
+1
--
Salut,
Jordi.
[EMAIL PROTECTED] wrote:
I'm pretty committed to the idea that JMeter 2.0 will be drastically different from JMeter 1.9.
So, feel free to make big changes.
Hey, Mike, we'd like to know what you're thinking about?
--
Salut,
Jordi.
Thanks to both Jeremy and Jordi for finding and fixing these problems. I also
fixed the lack of jdom.jar in the release. The src files are out there, however,
wouldn't it be preferable for the src dist to be a mirror of the files as they
appear in CVS? As it is now, someone can download the
BAZLEY, Sebastian wrote:
Aside: some of these e-mail trails are getting quite long - how about using
the Wiki to collate the information?
Not at this stage -- we did that in the past and was fun, but not very
successful. It looks like a good place to create documentation, but not
quite a good
, 2003 2:47 PM
Subject: Re: Source dist build
Thanks to both Jeremy and Jordi for finding and fixing these problems. I also
fixed the lack of jdom.jar in the release. The src files are out there, however,
wouldn't it be preferable for the src dist to be a mirror of the files as they
appear in CVS
...
-Original Message-
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 12 August 2003 12:36
To: JMeter Developers List
Subject: Re: AW: JMeter 2.0 [Re: Source dist build]
Following Mike's prompt, I've been reading a little bit about socket
factories, etc. and I now believe it can
Hello,
In principle, I agree with everything Sebastian said...at least for
the src versions. (I still have to think about his comments on the
binary versions.) Mike is correct about JMeter having a different
target audience than most Jakarta projects. However, I think that the
Following Mike's prompt, I've been reading a little bit about socket
factories, etc. and I now believe it can be done -- although it's
probably difficult (or even very difficult).
Here's my view of it:
We replace the socket factory with one producing our own sockets. These
sockets should do
Hi all,
great ideas getting exchanged here between Mike, Jordi and Jeremy...
I think seperation of tasks like Jordi mentioned would be a good think. I also highly
welcome the idea of datasources by Mike. This would increase flexibility a lot.
by Jordi:
Totally agree. The complete split
Hi Mike. Hi everyone.
./build.sh src_dist has some problems (in addition to the one I
described in my previous message). Enumerating them here for discussion:
- The src distribution needs to be unpacked on top of the binary
distribution -- otherwise the libraries in lib/ will be missing. Do you
[EMAIL PROTECTED] wrote:
I've been using JMeter as a user quite a bit the past few weeks, and I've learned some things
about it. One is that it's very tedious to use, and so a lot of my thoughts have to do with
creating more powerful tools to manipulate test scripts. I think I'd like to
Regarding Wiki, here's my thoughts:
A lot of the old stuff is probably not worth updating, and should probably be put into
some
obsolete area.
As far as team planning goes, I'd like to encourage people to be aggressive and
fearless in
pursuing changes. With some caveats:
1. Things that are
[EMAIL PROTECTED] wrote:
I'm thinking src_dist should simply tar up all the cvs files as is and be done.
What do you all think?
Pros: can build immediately after downloading. Is easy to create and
maintain the ant rules.
Cons: is bulky.
I think the pros outweight the cons.
--
Salut,
Jordi.
It's always nice to see other people thinking in the same general
directions that I am.
I think Jordi is on the right track about having a separate analysis
component. I would like to keep the Visualizers out of the Test Plan --
leave the Test Plan with the job of describing the test. Make
Mike,
Jordi did all the work -- I just spent 5 minutes having Eclipse look
for where methods were called from.
Getting a dump of CVS sounds like a reasonable plan for this
release. But this might be something to discuss for the next release.
Moving to Maven might make it a moot point
16 matches
Mail list logo
