From bxxpwg-admin@lists.invisibleworlds.com Mon Apr 9 23:35:58 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA24251 for ; Mon, 9 Apr 2001 23:35:54 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id UAA07326; Mon, 9 Apr 2001 20:34:36 -0700 (PDT) Received: from fep6.online.sh.cn ([202.96.209.79]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id UAA07312 for ; Mon, 9 Apr 2001 20:34:30 -0700 (PDT) From: JohnnyXia@acersoftech.com.cn Received: from cnshans1.acersoftech.com.cn ([202.96.233.98]) by fep6.online.sh.cn (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010410033451.BAY460.fep6.online.sh.cn@cnshans1.acersoftech.com.cn> for ; Tue, 10 Apr 2001 11:34:51 +0800 Received: by cnshans1.acersoftech.com.cn(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 48256A2A.001406B8 ; Tue, 10 Apr 2001 11:38:44 +0800 X-Lotus-FromDomain: ACER To: bxxpwg@lists.invisibleworlds.com Message-ID: <48256A2A.001405ED.00@cnshans1.acersoftech.com.cn> Date: Tue, 10 Apr 2001 11:36:05 +0800 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [BXXPwg] Maxium Size of the frame payload. Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Hi all, The mail list has been silent for a long time. Is there still anyone focusing on this protocol? These days I am devoting to write a BEEP library with C++. In my codes, I assume that the size of the frame payload is no bigger than 2K. Later I review the spec(RFC3080), it hasn't any authorative statement on the maxium frame payload size.I think this is important in implementation. I can't accept any size of a frame. There must be a upper limit. But what is it? Thanks in advance. Johnny Xia. _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Tue Apr 10 00:15:11 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24502 for ; Tue, 10 Apr 2001 00:15:10 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07540; Mon, 9 Apr 2001 21:14:07 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07524 for ; Mon, 9 Apr 2001 21:14:07 -0700 (PDT) Received: from wilson (cpe-66-1-176-103.ut.sprintbbd.net [66.1.176.103]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id VAA26259 for ; Mon, 9 Apr 2001 21:13:41 -0700 (PDT) Message-ID: <003401c0c174$7fb37b90$0100a8c0@wilson> From: "Huston" To: References: <48256A2A.001405ED.00@cnshans1.acersoftech.com.cn> Subject: Re: [BXXPwg] Maxium Size of the frame payload. Date: Mon, 9 Apr 2001 22:10:26 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Content-Transfer-Encoding: 7bit The upper limit is based on the transport mapping. For the TCP mapping (RFC3081) the largest frame is the size of the advertised window for the channel. By default this is 4k. BTW, there is quite a bit of activity around the protocol. Check out the beep related projects on sourceforge.net and www.beepcore.org. --Huston ----- Original Message ----- From: To: Sent: Monday, April 09, 2001 9:36 PM Subject: [BXXPwg] Maxium Size of the frame payload. > > > Hi all, > > The mail list has been silent for a long time. Is there still anyone focusing on > this protocol? > > These days I am devoting to write a BEEP library with C++. In my codes, I assume > that the size > of the frame payload is no bigger than 2K. Later I review the spec(RFC3080), it > hasn't any authorative > statement on the maxium frame payload size.I think this is important in > implementation. I can't accept > any size of a frame. There must be a upper limit. But what is it? > > Thanks in advance. > > Johnny Xia. > > > > _______________________________________________ > BXXPwg mailing list > BXXPwg@lists.invisible.net > http://lists.invisible.net/mailman/listinfo/bxxpwg _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Tue Apr 10 00:15:42 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24515 for ; Tue, 10 Apr 2001 00:15:42 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07584; Mon, 9 Apr 2001 21:14:39 -0700 (PDT) Received: from snowhite.cis.temple.edu (snowhite.cis.temple.edu [155.247.190.207]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07567 for ; Mon, 9 Apr 2001 21:14:38 -0700 (PDT) Received: from snowhite.cis.temple.edu (cgraham@snowhite.cis.temple.edu [155.247.190.207]) by snowhite.cis.temple.edu (8.9.3/8.9.3) with ESMTP id AAA27120 for ; Tue, 10 Apr 2001 00:14:38 -0400 (EDT) Date: Tue, 10 Apr 2001 00:14:37 -0400 (EDT) From: Charles Graham To: Subject: Re: [BXXPwg] Maxium Size of the frame payload. In-Reply-To: <48256A2A.001405ED.00@cnshans1.acersoftech.com.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net I am a begginer, so please beer with me guys. Maybe I am mistaken, but why is it that you asume that there has to be a maximum size for a payload frame? The transport service mapping makes sure that all frames are dilivered to the respective BEEP peer as a whole. Do we want to put restrictions on the users as to how much they can send at a time? If so, why? I thought that one of the good things about BEEP was that it provided an abstraction so that we can send messages and frames of any size and be sure that they would come out on the other end in tact without worrying about how the underlying transport protocal does (or in the case of TCP, does not do) the framing. Respectfully, Charles Graham On Tue, 10 Apr 2001 JohnnyXia@acersoftech.com.cn wrote: > > > Hi all, > > The mail list has been silent for a long time. Is there still anyone focusing on > this protocol? > > These days I am devoting to write a BEEP library with C++. In my codes, I assume > that the size > of the frame payload is no bigger than 2K. Later I review the spec(RFC3080), it > hasn't any authorative > statement on the maxium frame payload size.I think this is important in > implementation. I can't accept > any size of a frame. There must be a upper limit. But what is it? > > Thanks in advance. > > Johnny Xia. > > > > _______________________________________________ > BXXPwg mailing list > BXXPwg@lists.invisible.net > http://lists.invisible.net/mailman/listinfo/bxxpwg > _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Tue Apr 10 00:25:47 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24642 for ; Tue, 10 Apr 2001 00:25:47 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07690; Mon, 9 Apr 2001 21:24:43 -0700 (PDT) Received: from dbc.mtview.ca.us (ppp-63-207-83-130.ded.pacbell.net [63.207.83.130]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07672 for ; Mon, 9 Apr 2001 21:24:43 -0700 (PDT) Received: from FATORA (ppp-63-207-83-135.ded.pacbell.net [63.207.83.135]) by dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id f3A43ep25181; Mon, 9 Apr 2001 21:03:40 -0700 (PDT) Message-ID: <039c01c0c176$1811b810$8753cf3f@FATORA> From: "Marshall T. Rose" To: , Cc: "Marshall Rose" References: <48256A2A.001405ED.00@cnshans1.acersoftech.com.cn> Subject: Re: [BXXPwg] Maxium Size of the frame payload. Date: Mon, 9 Apr 2001 21:24:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Content-Transfer-Encoding: 7bit > The mail list has been silent for a long time. Is there still anyone focusing on > this protocol? look at http://beepcore.org/ > These days I am devoting to write a BEEP library with C++. In my codes, I assume > that the size > of the frame payload is no bigger than 2K. Later I review the spec(RFC3080), it > hasn't any authorative > statement on the maxium frame payload size.I think this is important in > implementation. I can't accept > any size of a frame. There must be a upper limit. But what is it? i see several places that talk about a hard limit, viz., common = channel SP msgno SP more SP seqno SP size channel = 0..2147483647 msgno = 0..2147483647 more = "." / "*" seqno = 0..4294967295 size = 0..2147483647 ansno = 0..2147483647 tells me that an individual frame has between 0 and ~2GB octets. of course, flow control (c.f., RFC 3081) might impose limits as well... /mtr _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Tue Apr 10 00:36:37 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24795 for ; Tue, 10 Apr 2001 00:36:36 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07818; Mon, 9 Apr 2001 21:35:31 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id VAA07799 for ; Mon, 9 Apr 2001 21:35:30 -0700 (PDT) Received: from wilson (cpe-66-1-176-103.ut.sprintbbd.net [66.1.176.103]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id VAA14230 for ; Mon, 9 Apr 2001 21:35:27 -0700 (PDT) Message-ID: <004001c0c177$89d99160$0100a8c0@wilson> From: "Huston" To: References: Subject: Re: [BXXPwg] Maxium Size of the frame payload. Date: Mon, 9 Apr 2001 22:34:30 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Content-Transfer-Encoding: 7bit BEEP does allow for sending messages of any size. However, to allow multiple channels to be multiplexed over a single connection with some level of fairness the messages are divided into frames. Frames can not be any size because one of the reasons for having frames is to prevent one channel from monopolizing the connection. So frame size is determined by the transport mapping based on what is best for the particular transport. In the TCP mapping it states that a peer can only send a frame as large as the amount of available channel window. --Huston ----- Original Message ----- From: "Charles Graham" To: Sent: Monday, April 09, 2001 10:14 PM Subject: Re: [BXXPwg] Maxium Size of the frame payload. > I am a begginer, so please beer with me guys. > > Maybe I am mistaken, but why is it that you asume that there has to be a > maximum size for a payload frame? The transport service mapping makes > sure that all frames are dilivered to the respective BEEP peer as a whole. > Do we want to put restrictions on the users as to how much they can send > at a time? If so, why? > > I thought that one of the good things about BEEP was that it provided an > abstraction so that we can send messages and frames of any size and be > sure that they would come out on the other end in tact without worrying > about how the underlying transport protocal does (or in the case of TCP, > does not do) the framing. > > Respectfully, > Charles Graham > > On Tue, 10 Apr 2001 JohnnyXia@acersoftech.com.cn wrote: > > > > > > > Hi all, > > > > The mail list has been silent for a long time. Is there still anyone focusing on > > this protocol? > > > > These days I am devoting to write a BEEP library with C++. In my codes, I assume > > that the size > > of the frame payload is no bigger than 2K. Later I review the spec(RFC3080), it > > hasn't any authorative > > statement on the maxium frame payload size.I think this is important in > > implementation. I can't accept > > any size of a frame. There must be a upper limit. But what is it? > > > > Thanks in advance. > > > > Johnny Xia. > > > > > > > > _______________________________________________ > > BXXPwg mailing list > > BXXPwg@lists.invisible.net > > http://lists.invisible.net/mailman/listinfo/bxxpwg > > > > > _______________________________________________ > BXXPwg mailing list > BXXPwg@lists.invisible.net > http://lists.invisible.net/mailman/listinfo/bxxpwg _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Apr 30 18:17:40 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27228 for ; Mon, 30 Apr 2001 18:17:38 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id PAA29255; Mon, 30 Apr 2001 15:15:43 -0700 (PDT) Received: from invisible.net (qawoor.not.invisible.net [204.62.247.23]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id PAA29241 for ; Mon, 30 Apr 2001 15:15:43 -0700 (PDT) Received: from ballistic (c525276-a.ptlum1.sfba.home.com [24.20.129.105]) by invisible.net (8.9.3/8.9.3) with SMTP id PAA02540; Mon, 30 Apr 2001 15:09:22 -0700 (PDT) Message-ID: <009b01c0d1c3$1a356a30$1900a8c0@ballistic> From: "Kristopher Magnusson" To: Date: Mon, 30 Apr 2001 15:15:44 -0700 Organization: Invisible Worlds, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Subject: [BXXPwg] Beepcore.org: resources for the BEEP community Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Content-Transfer-Encoding: 7bit Invisible Worlds has launched the new BEEP-related web site, Beepcore.org (http://www.beepcore.org/). BEEP is a proposed Internet standard for developing new application-layer protocols (RFC 3080 and RFC 3081). Beepcore.org has the most recent information about BEEP, including: -- a directory of BEEP developers -- a directory of BEEP-compatible commercial products; and -- a directory of BEEP-related software projects. -- new IETF I-Ds and RFCs; -- white papers and presentations about BEEP; -- an updated Q&A with Dr. Rose Beepcore.org is already listing some interesting new projects. Gabe Wachob has kicked off his PyBeep project, which is an implementation of a BEEP library in Python. Ben Feinstein is the admin of the new IDXP-Java project, which is an application-layer protocol for exchanging data between intrusion detection entities. Some enterprising folks at Temple University are working on HSTP (Hypertext Streaming Transfer Protocol), essentially HTTP over BEEP that takes advantage of multiple channels. And our very own development team has released open source implementations of Beepcore-Java and Beepcore-Tcl, and has updated the Ethereal packet dumper for network analysis to reflect RFCs 3080 and 3081. If you're interested in BEEP-related consulting, don't forget to add yourself to the BEEP developer's directory. Also, if you're working on a new BEEP application profile or a commercial application, be sure to list it in the BEEP projects or products directory. The way the development hosting works is a little different than BXXP.org. Rather than maintain our own CVS and bug tracking infrastructure, Invisible Worlds hosts its CVS trees and mailing lists at SourceForge, which enables us to concentrate on, well, building more BEEP stuff rather than maintaining web sites. Now we include information about a particular project in the directory of projects, and link to the external URLs at SourceForge. The web site is completely database-driven and is administrated distributed-style by the BEEP developer community. As a side note, Invisible Worlds will be retiring the old BXXP.org web site soon, as well as end-of-lifing the SpaceKits. While the site's still up, you're welcome to download and use any code there, but in the future we will probably not make it generally available for download, and will not be supporting it as of today. Have fun with the new site! ............ kris Kris Magnusson kris@invisible.net, Invisible Worlds, Inc. (http://www.invisible.net/) Site Manager, Beepcore.org (http://www.beepcore.org) _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Apr 30 18:55:28 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27813 for ; Mon, 30 Apr 2001 18:55:27 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id PAA29519; Mon, 30 Apr 2001 15:54:24 -0700 (PDT) Received: from xomi.pair.com (xomi.pair.com [209.68.2.14]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with SMTP id PAA29496 for ; Mon, 30 Apr 2001 15:54:22 -0700 (PDT) Received: (qmail 57104 invoked by uid 3039); 30 Apr 2001 22:54:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Apr 2001 22:54:16 -0000 Date: Mon, 30 Apr 2001 15:54:16 -0700 (PDT) From: Gabe Wachob X-Sender: To: Kristopher Magnusson cc: Subject: Re: [BXXPwg] Beepcore.org: resources for the BEEP community In-Reply-To: <009b01c0d1c3$1a356a30$1900a8c0@ballistic> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net On Mon, 30 Apr 2001, Kristopher Magnusson wrote: > Beepcore.org is already listing some interesting new projects. Gabe Wachob > has kicked off his PyBeep project, which is an implementation of a BEEP > library in Python. Gabe would like to invite all persons interested to Python to get involved. I am actively looking for an enthusiastic co-leader for this project as its is not gettting enough attention from me! > If you're interested in BEEP-related consulting, don't forget to add > yourself to the BEEP developer's directory. WiredObjects is interested in taking on outsourced BEEP related projects. Please contact me if you might have needs here > As a side note, Invisible Worlds will be retiring the old BXXP.org web site > soon, as well as end-of-lifing the SpaceKits. While the site's still up, > you're welcome to download and use any code there, but in the future we will > probably not make it generally available for download, and will not be > supporting it as of today. This is a big announcement! Will there be any implementations of BEEP available open there besides mine (which is not complete) and the Apache module? -Gabe _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Apr 30 18:56:21 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27831 for ; Mon, 30 Apr 2001 18:56:20 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id PAA29564; Mon, 30 Apr 2001 15:55:17 -0700 (PDT) Received: from xomi.pair.com (xomi.pair.com [209.68.2.14]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with SMTP id PAA29550 for ; Mon, 30 Apr 2001 15:55:17 -0700 (PDT) Received: (qmail 57295 invoked by uid 3039); 30 Apr 2001 22:55:15 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Apr 2001 22:55:15 -0000 Date: Mon, 30 Apr 2001 15:55:15 -0700 (PDT) From: Gabe Wachob X-Sender: To: Kristopher Magnusson cc: Subject: Re: [BXXPwg] Beepcore.org: resources for the BEEP community In-Reply-To: <009b01c0d1c3$1a356a30$1900a8c0@ballistic> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Ah, sorry, the beepcore projects are alive - its the spacekits that are dying. Fair enough, sorry for the noise. -Gabe _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Apr 30 19:03:43 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27939 for ; Mon, 30 Apr 2001 19:03:43 -0400 (EDT) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id QAA29668; Mon, 30 Apr 2001 16:02:40 -0700 (PDT) Received: from invisible.net (qawoor.not.invisible.net [204.62.247.23]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id QAA29655 for ; Mon, 30 Apr 2001 16:02:39 -0700 (PDT) Received: from ballistic (c525276-a.ptlum1.sfba.home.com [24.20.129.105]) by invisible.net (8.9.3/8.9.3) with SMTP id PAA02697; Mon, 30 Apr 2001 15:55:51 -0700 (PDT) Message-ID: <004101c0d1c9$989cd2e0$1900a8c0@ballistic> From: "Kristopher Magnusson" To: "Gabe Wachob" Cc: References: Subject: Re: [BXXPwg] Beepcore.org: resources for the BEEP community Date: Mon, 30 Apr 2001 16:02:13 -0700 Organization: Invisible Worlds, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Content-Transfer-Encoding: 7bit Just want to clarify--the SpaceKits are being replaced by Beepcore impls. We have already released Beepcore-Java and Beepcore-Tcl under the BPL. We have announced a Beepcore-C implementation that will be released later. Have fun! ............ kris ----- Original Message ----- From: "Gabe Wachob" To: "Kristopher Magnusson" Cc: Sent: Monday, April 30, 2001 3:54 PM Subject: Re: [BXXPwg] Beepcore.org: resources for the BEEP community > On Mon, 30 Apr 2001, Kristopher Magnusson wrote: > > > Beepcore.org is already listing some interesting new projects. Gabe Wachob > > has kicked off his PyBeep project, which is an implementation of a BEEP > > library in Python. > > Gabe would like to invite all persons interested to Python to get > involved. I am actively looking for an enthusiastic co-leader for this > project as its is not gettting enough attention from me! > > > If you're interested in BEEP-related consulting, don't forget to add > > yourself to the BEEP developer's directory. > > WiredObjects is interested in taking on outsourced BEEP related > projects. Please contact me if you might have needs here > > > As a side note, Invisible Worlds will be retiring the old BXXP.org web site > > soon, as well as end-of-lifing the SpaceKits. While the site's still up, > > you're welcome to download and use any code there, but in the future we will > > probably not make it generally available for download, and will not be > > supporting it as of today. > > This is a big announcement! Will there be any implementations of BEEP > available open there besides mine (which is not complete) and the Apache > module? > > -Gabe > > > _______________________________________________ > BXXPwg mailing list > BXXPwg@lists.invisible.net > http://lists.invisible.net/mailman/listinfo/bxxpwg > _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg