Troy,
Beepcore-java doesn't have any limits on message sizes. If you are not using
the code in CVS, my guess is that you are reading the message in the
receiveXXX callback or you are replying to a MSG in the callback to
receiveMSG. This will block the IO thread so new frames can not be received.
The code in CVS doesn't have this problem but if you want to use the
released code try using the MessageQueue or Reply classes in lib or start
your own thread in the receiveXXX callback to read the message.
--Huston
----- Original Message -----
From: <no...@co...>
To: <bee...@li...>
Sent: Monday, October 20, 2003 7:16 AM
Subject: [Beepcore-java-users] max message size
> Hello,
>
> Does beepcore-j limit the amount of data sent in a MSG or RPY? I noticed
> getMaxFrameSize() is hardcoded to 1400 - is this the maximum byte[] size I
> can place inside an OutputDataStream?
>
> When I first began using beepcore-j, the replies were roughly 500 bytes.
> Now my reply size has grown to about 2k and the client does not receieve
> the replies. Do I need to break the message into smaller pieces myself,
> or is it that I am doing something wrong?
>
> I'm replying using message.sendRPY(new ByteOutputDataStream(data)), where
> data is a byte[] representation of an XML document.
>
> Thanks!
>
> Troy
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by OSDN developer relations
> Here's your chance to show off your extensive product knowledge
> We want to know what you know. Tell us and you have a chance to win $100
> http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
> _______________________________________________
> Beepcore-java-users mailing list
> Bee...@li...
> https://lists.sourceforge.net/lists/listinfo/beepcore-java-users
>
>
|
