Magnusson, Geir wrote:
-----Original Message-----
From: Andrew Zhang [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 6:11 AM
To: harmony-dev@incubator.apache.org; [EMAIL PROTECTED]
Subject: Re: [classlib] jetty based tests
If I understand correctly, it means Jetty selects a free port
from system,
and provides an API method (e.g. getJettyPort()) to get the
selected port.
In this way, listen port confliction issue could be
completely avoided.
Only once in my life have I seen a server randomly choose a port to
listen on, and I quickly took that engineer off networking projects for
a while :)
I didn't mean this the way it sounds to me now :) Sorry. I can also
see some uses for this. My example from my personal history was for
high-performance production code, so you can see why I had a rather
reflexive reaction...
Still, I think there are a few problems with the above, such as having
to have Jetty in the same process space, tying the test code to Jetty,
and of course, the repeatability.
I do see the utility of this though for convenience in some cases, and
if we decide to do a runtime port selection, I'd have a helper do it and
pass the selected port to both Jetty as well as the test code, so that
the two things are decoupled.
geir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
