On Wed, 2007-06-13 at 12:04 +0200, Remy Maucherat wrote: > Costin Manolache wrote: > >> setTimeout() is not optional (the javadoc is out of date, sorry), there > >> was an agreement on that earlier. Timeout sets the connection timeout, > >> which is most likely useful even if there are events. It's quite > >> possible sleep could use a timeout argument (I think calling setTimeout > >> is more or less mandatory when using sleep, and OTOH calling setTimout > >> is not as important otherwise). > > > > Ok - then sleep needs the extra argument, and will mean same as > > Thread.sleep(), > > but > > not-blocking ? > > This sleep is a non blocking call, and instructs the connection to "do > nothing until I wake you up (or a timeout occurs, of course)".
may be sleep is not the right name... Would suspend be a better name? Cheers Jean-Frederic --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
