From beepwg-admin@lists.beepcore.org Mon Oct 20 06:27:16 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20112 for ; Mon, 20 Oct 2003 06:27:13 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with ESMTP id h9KAOisw003195; Mon, 20 Oct 2003 03:24:49 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with SMTP id h9KAMtsw003173 for ; Mon, 20 Oct 2003 03:22:56 -0700 (PDT) Received: (qmail 23487 invoked by uid 0); 20 Oct 2003 10:22:50 -0000 Received: from 212.117.81.34 by www4.gmx.net with HTTP; Mon, 20 Oct 2003 12:22:50 +0200 (MEST) From: "Ingo Funken" To: beepwg@lists.beepcore.org MIME-Version: 1.0 X-Priority: 3 (Normal) X-Authenticated: #19191783 Message-ID: <3720.1066645370@www4.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Subject: [BEEPwg] About the two states in the BEEP Profile for SOAP Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Mon, 20 Oct 2003 12:22:50 +0200 (MEST) Content-Transfer-Encoding: 8bit Hello BEEP-WG, my question is about the boot and ready state in rfc 3288. Do these states concern only the session? Or do these states exist for every channel we create? Many thanks, Ufuk -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Mon Oct 20 14:54:25 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07592 for ; Mon, 20 Oct 2003 14:54:24 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with ESMTP id h9KIqSVX002704; Mon, 20 Oct 2003 11:52:33 -0700 (PDT) Received: from wbm2.pair.net (wbm2.pair.net [209.68.3.43]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with SMTP id h9KIpSVX002691 for ; Mon, 20 Oct 2003 11:51:28 -0700 (PDT) Received: (qmail 52823 invoked by uid 65534); 20 Oct 2003 18:51:20 -0000 Received: from 146.180.106.194 ([146.180.106.194]) (SquirrelMail authenticated user nospam@corporatefallout.com) by webmail.pair.com with HTTP; Mon, 20 Oct 2003 14:51:20 -0400 (EDT) Message-ID: <34236.146.180.106.194.1066675880.squirrel@webmail.pair.com> From: To: X-pair-Authenticated: 146.180.106.194 X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [BEEPwg] beepcore implementation Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Mon, 20 Oct 2003 14:51:20 -0400 (EDT) Content-Transfer-Encoding: 8bit Hi, Does beepcore-j limit the size on messages (in particular ANS & RPY). I recently began using beepcore-j, and initially my messages were roughly 500 bytes and everything worked very well. The message size has now grown to about 5k, and after a few messages, the processing stops, as if receiveANS and receiveRPY are no longer being called. I tried spawning a new thread to handle read the message input stream, and it didn't seem to help very much. Do I need to break the messages up into smaller pieces, or am I doing something else incorrectly? Thanks for any help! Troy _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Mon Oct 20 15:41:24 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20739 for ; Mon, 20 Oct 2003 15:41:23 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with ESMTP id h9KJf2VX003139; Mon, 20 Oct 2003 12:41:02 -0700 (PDT) Received: from act-of-god.permabit.com (act-of-god.permabit.com [67.107.99.100]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with ESMTP id h9KJeDVX003129 for ; Mon, 20 Oct 2003 12:40:14 -0700 (PDT) Received: from questionably-configured.permabit.com.permabit.com (questionably-configured.permabit.com [10.0.8.28]) by act-of-god.permabit.com (Postfix) with ESMTP id 6261413ACB; Mon, 20 Oct 2003 15:40:03 -0400 (EDT) To: Cc: Subject: Re: [BEEPwg] beepcore implementation References: <34236.146.180.106.194.1066675880.squirrel@webmail.pair.com> From: Jered Floyd In-Reply-To: <34236.146.180.106.194.1066675880.squirrel@webmail.pair.com> Message-ID: <87u163zoj0.fsf@questionably-configured.permabit.com> Lines: 56 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: 20 Oct 2003 15:40:03 -0400 > Does beepcore-j limit the size on messages (in particular ANS & RPY). I > recently began using beepcore-j, and initially my messages were roughly > 500 bytes and everything worked very well. The message size has now grown > to about 5k, and after a few messages, the processing stops, as if > receiveANS and receiveRPY are no longer being called. I tried spawning a > new thread to handle read the message input stream, and it didn't seem to > help very much. Do I need to break the messages up into smaller pieces, > or am I doing something else incorrectly? Troy, You probably want the list "beepcore-java-users@lists.sourceforge.net"; this list is for discussion of the BEEP protocol as opposed to its implementations. That said, the problem is that you will deadlock with the remote peer if you try to read in a complete message with receiveMSG() when it is called, because the thread that calls receiveMSG() is also responsible for sending out SEQs as data is read in to your application. If you ever receive a message that is larger than the channel window buffer size, your application will fail to read it in, waiting for more data that will never come (until you return and let the thread do its housekeeping.) Attached is a message from the beepcore-java-users list regarding this problem; I believe it is the same as you are seeing. --Jered From: Jered Floyd Subject: Re: [Beepcore-java-users] any solution to handle multiple frames? To: "Cao, Ben P" Cc: "'beepcore-java-users@lists.sourceforge.net'" Date: 13 Sep 2001 15:28:38 -0400 "Cao, Ben P" writes: > I now have problem with message being sent that is greater than 4K. I > noticed that there is one previous posting and resolution to the problem by > Huston for the next release version of Beep. However, does anyone find a way > to deal with this at all? I am trying to fix it, but unsuccessful. Yes; to work around this for the time being, make sure that the read() on the input streams occurs in a different thread from the SessionThread, which is where receiveMSG() is called. Have your receiveMSG() give the Message object to another thread for processing (i.e. store it in an instance field and notify() to wake a different thread that is wait()ing on the Message, or what-have-you.) Beepcore provides MessageQueue, which may be able to help you here. Register a MessageQueue (instead of your current class) as the MessageListener, and have your class take the Messages from the Queue from a separate thread. --Jered _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Mon Oct 20 19:07:03 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13125 for ; Mon, 20 Oct 2003 19:07:03 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with ESMTP id h9KN6RVX004685; Mon, 20 Oct 2003 16:06:28 -0700 (PDT) Received: from drakken.dbc.mtview.ca.us ([65.125.189.56]) by qawoor.dbc.mtview.ca.us (8.12.10/8.12.9) with ESMTP id h9KN4lVX004660 for ; Mon, 20 Oct 2003 16:04:47 -0700 (PDT) Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h9KN4UQP002246; Mon, 20 Oct 2003 16:04:30 -0700 (PDT) From: Marshall Rose To: "Ingo Funken" Cc: beepwg@lists.beepcore.org Subject: Re: [BEEPwg] About the two states in the BEEP Profile for SOAP Message-Id: <20031020160430.261d51e1.mrose@dbc.mtview.ca.us> In-Reply-To: <3720.1066645370@www4.gmx.net> References: <3720.1066645370@www4.gmx.net> Organization: Dover Beach Consulting, Inc. X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Mon, 20 Oct 2003 16:04:30 -0700 Content-Transfer-Encoding: 7bit > Hello BEEP-WG, > my question is about the boot and ready state in rfc 3288. Do these states > concern only the session? Or do these states exist for every > channel we create? it pertains to each channel. the reason, of course, is that the bootmsg sent in the boot state may request a different resource for each channel... /mtr _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg