beepcore-java-users — Discussion list for developers using beepcore-java library

[Beepcore-java-users] Stalling in sendMSG

[William J. M. <wm...@ol...>]

I appear to be hitting a condition where I stall in sendMSG when 
I have put more than 4K on the output datastream to send.
Looking at the conversation as it goes by, the RPY starts
being sent, and I get the first 3 frames, the recieving end
is sending SEQ frames and opening the window properly, but
the sendMSG function aparently stalls after sending 4K of
data.  Should'nt the SEQ's be getting processed?

Is this a known problem?


-bill

Re: [Beepcore-java-users] Problems encountered in running "beepd" and "beepng"

[Huston <hu...@us...>]

MessageRonald,

Mark Richardson found this bug and has fixed it but the fix has not been
checked in because of some other changes happening this week. I expect the
fix should be checked in by Monday of next week.

BTW, for beepcore-c questions please use the beepcore-c-users mailing list.

Thanks,
--Huston

----- Original Message -----
From: Ronald Wong
To: bee...@li...
Sent: Monday, January 14, 2002 11:53 PM
Subject: [Beepcore-java-users] Problems encountered in running "beepd" and
"beepng"


Hi all,

    I have downloaded the lastest version of beepcore-c though CVS and
compiled it by the "configure" script and then "make". After then I try to
run the "beepd" and "beepng". However there was sementation fault happened
for the "beepng" while it is going to finish the task.

    I used the command "$ beepd -f
./fyp/beepcore-c/threaded_os/examples/unix/beepd.cfg" to start the "beepd"
and the command "beepng -f
./fyp/beepcore-c/threaded_os/examples/unix/beepd.cfg -p 10289 192.168.0.1"
to start the beepng.

    Is there any one of you know what is going wrong for my command / config
/ setting ? Attached is the screen dump, the log and the config file.

Thanks a lot.
Ronald

Re: [Beepcore-java-users] BEEP JAVA Implementation

[Huston <hu...@us...>]

Randeep,

Currently there isn't any design documentation. Other than looking at the
code you can ask questions on this mailing list or to me directly or wait
for Marshall's BEEP book to be published.

--Huston

----- Original Message -----
From: "Randeep Singh" <rs...@in...>
To: <bee...@li...>
Sent: Tuesday, January 01, 2002 11:16 PM
Subject: [Beepcore-java-users] BEEP JAVA Implementation


I am a software programmer going through Beep-Java Implementation.I
really appreciate the way it has been implemented.
Has any one of us generated any kind of design document for the
BEEP-JAVA Implementation.It will be nice to have components and design
Architecture in order to have proper understanding of this
Implementation.I tried to generate the Class Diagram from Rational Rose
but it coudln't generate that.

Regards
Randeep

_______________________________________________
Beepcore-java-users mailing list
Bee...@li...
https://lists.sourceforge.net/lists/listinfo/beepcore-java-users

[Beepcore-java-users] BEEP JAVA Implementation

[Randeep S. <rs...@in...>]

I am a software programmer going through Beep-Java Implementation.I
really appreciate the way it has been implemented.
Has any one of us generated any kind of design document for the
BEEP-JAVA Implementation.It will be nice to have components and design
Architecture in order to have proper understanding of this
Implementation.I tried to generate the Class Diagram from Rational Rose
but it coudln't generate that.

Regards
Randeep=20

Re: [Beepcore-java-users] API changes - DataStreams

[Antal A. <at...@no...>]

> I'm planning on adding a new FileOutputDataStream as well as
> InputStreamOutputDataStream (this needs a new name, suggestions are welco=
me)
> in the lib package.
>=20
> --Huston
>=20

I am waiting for it, my application crashes without the
ex-InputStreamDataStream.
I vote for InputStreamOutputDataStream as IOPipedDataStream or
I2ODataStream

atech

Re: [Beepcore-java-users] API changes - DataStreams

[Huston <hu...@us...>]

> I've just started incorporating the changes in the streams stuff into
> the app I am working on and thought now might be a good time to bring up
> a few things.  I'll assume the current cvs tree might not yet be
> complete?

Yes, the code in cvs is a work in progress.

> (1) OutputDataStream - a helpful addition would be able to treat the
> OutputDataStream as if it were a java.io.OutputStream.  In one case, I
> XSLT transform a document to an java.io.OutputStream, it would make
> sense to parse to the output stream used by the sendMSG.  From an API
> viewpoint, a constructor along the lines of
> OutputDataStream(java.io.OutputStream) would be nice.

I was planning on having a sub-class of OutputDataStream in the lib package
that would provide this functionality. I haven't implemented this yet
because to do it correctly I need one of the fixes I'm currently working on.

> In another point in my app, I send a file as the payload of a message.
> Under the current cvs, I believe I would need to read this file into a
> byte[] and then use the byte[] to construct a ByteDataStream.  In this
> case I would rather buffer read the file and write to an
> OutputDataStream.  The sendMSG would pump the data until the
> OutputDataStream were closed (or setComplete()).  The old
> org.beepcore.beep.core.FileDataStream was actually great for this.

I'm planning on adding a new FileOutputDataStream as well as
InputStreamOutputDataStream (this needs a new name, suggestions are welcome)
in the lib package.

--Huston

[Beepcore-java-users] API changes - DataStreams

[Tom D. <vze...@ve...>]

I've just started incorporating the changes in the streams stuff into
the app I am working on and thought now might be a good time to bring up
a few things.  I'll assume the current cvs tree might not yet be
complete?

(1) OutputDataStream - a helpful addition would be able to treat the
OutputDataStream as if it were a java.io.OutputStream.  In one case, I
XSLT transform a document to an java.io.OutputStream, it would make
sense to parse to the output stream used by the sendMSG.  From an API
viewpoint, a constructor along the lines of
OutputDataStream(java.io.OutputStream) would be nice.

In another point in my app, I send a file as the payload of a message. 
Under the current cvs, I believe I would need to read this file into a
byte[] and then use the byte[] to construct a ByteDataStream.  In this
case I would rather buffer read the file and write to an
OutputDataStream.  The sendMSG would pump the data until the
OutputDataStream were closed (or setComplete()).  The old
org.beepcore.beep.core.FileDataStream was actually great for this.

(2) Should Session.fireEvent be public instead of protected - I have an
app class that has registered to listen for channel SessionEvents on a
given session.  When a new channel is started on the session I would
like to have my app receive the CHANNEL_OPENED_EVENT_CODE.  

I would like to have my StartChannelListener.startChannel fire the event
using
channel.getSession().fireEvent(SessionEvent.CHANNEL_OPENED_EVENT_CODE,channel);
 ... but Session.fireEvent is protected.

It seems to me that StartChannelListener.startChannel() is the
appropriate place to fire this event on behalf of the session (vs having
the session class fire the event), giving flexibility in the event data
up to the programmer (in my case passing off a reference to the channel
being created).

tom