Can you hand off the reply object to the reply handler thread? BEEP won't
care who deals with it.
On Tue, Aug 06, 2002 at 02:20:53PM -0700, Russell Hung wrote:
> Hi,
>
> I have a question about the input and output stream of BEEP. I read the
> example on the book, "BEEP", written by Dr. Marshall T. Rose and
> published by O'Reilly. There is a client example on page 52:
>
> try {
> channel.sendMSG(new StringOutputDataStream(request), reply);
> } catch { ....}
>
> InputDataStream ds = reply.getNextReply().getDataStream();
> InputStream is = ds.getInputStream();
>
> while(is.read() != -1) {
> ++replyLength;
> }
>
> It uses the message reply object to get the input stream. That means we
> have to send a message and wait for the response. This is not what I
> want. What I need are two independent threads: one for listening to the
> port/messages and one for sending out the message through the port. Is
> there any way to have an independent InputStream? Thanks.
>
> Best Regards,
>
> Russell Hung
> rh...@vi...
>
|
