From beepwg-bounces@dbc.mtview.ca.us Sat Apr 08 21:12:11 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FSOTL-0006cD-7e for beep-archive@lists.ietf.org; Sat, 08 Apr 2006 21:12:11 -0400 Received: from [168.143.123.173] (helo=drakken.dbc.mtview.ca.us) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSOTH-0000tS-OU for beep-archive@lists.ietf.org; Sat, 08 Apr 2006 21:12:11 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k391AneJ008787; Sat, 8 Apr 2006 18:10:51 -0700 Received: from priv-edtnes15.telusplanet.net (outbound04.telus.net [199.185.220.223])k391Aksp008784 for ; Sat, 8 Apr 2006 18:10:46 -0700 Received: from priv-edtnaa06.telusplanet.net ([154.20.166.96]) by priv-edtnes15.telusplanet.netESMTP <20060409011037.BHLE17317.priv-edtnes15.telusplanet.net@priv-edtnaa06.telusplanet.net> for ; Sat, 8 Apr 2006 19:10:37 -0600 Received: from ensemble.local (d154-20-166-96.bchsia.telus.net [154.20.166.96])Firewall) with ESMTP id EEE2HMHUBT for ; Sat, 8 Apr 2006 19:10:35 -0600 (MDT) Received: by ensemble.local (Postfix, from userid 501) id 927C756443F; Sat, 8 Apr 2006 18:09:32 -0700 (PDT) Date: Sat, 8 Apr 2006 18:09:32 -0700 From: Sam Roberts To: beepwg@lists.beepcore.org Message-ID: <20060409010932.GA862@ensemble.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: [BEEPwg] Any thoughts on BEEP over MPI? X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 I'm trying to figure out if MPI is a general enough message passing protocol that you could implement BEEP over it, and whether it would be a good idea. In particular, whether MPI could be faster than TCP. Any pointers or thoughts would be greatly appreciated. Thanks, Sam _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Sun Apr 09 12:12:25 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FScWX-0000bK-JA for beep-archive@lists.ietf.org; Sun, 09 Apr 2006 12:12:25 -0400 Received: from [168.143.123.173] (helo=drakken.dbc.mtview.ca.us) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FScWW-0004aq-7T for beep-archive@lists.ietf.org; Sun, 09 Apr 2006 12:12:25 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k39GAsub026665; Sun, 9 Apr 2006 09:10:56 -0700 Received: from localhost.localdomain (10.225.203.213.rev.inetbone.net [213.203.225.10])k39GAoRk026659 for ; Sun, 9 Apr 2006 09:10:50 -0700 Received: from localhost ([127.0.0.1] helo=[IPv6:::1]) by localhost.localdomain with esmtp (Exim 4.50) id 1FScUv-00039D-VA; Sun, 09 Apr 2006 09:10:46 -0700 In-Reply-To: <20060409010932.GA862@ensemble.local> References: <20060409010932.GA862@ensemble.local> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marshall Rose Subject: Re: [BEEPwg] Any thoughts on BEEP over MPI? Date: Sun, 9 Apr 2006 09:10:41 -0700 To: Sam Roberts X-Mailer: Apple Mail (2.746.3) cc: beepwg@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c > I'm trying to figure out if MPI is a general enough message passing > protocol that you could implement BEEP over it, and whether it would > be a good idea. In particular, whether MPI could be faster than TCP. > > Any pointers or thoughts would be greatly appreciated. MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something else? /mtr _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Sun Apr 09 14:05:14 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FSeHi-0005Q2-Rt for beep-archive@lists.ietf.org; Sun, 09 Apr 2006 14:05:14 -0400 Received: from [168.143.123.173] (helo=drakken.dbc.mtview.ca.us) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSeHh-0008GV-EB for beep-archive@lists.ietf.org; Sun, 09 Apr 2006 14:05:14 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k39I3qKm027711; Sun, 9 Apr 2006 11:03:54 -0700 Received: from priv-edtnes44.telusplanet.net (defout.telus.net [199.185.220.240])k39I3oqn027708 for ; Sun, 9 Apr 2006 11:03:50 -0700 Received: from priv-edtnaa05.telusplanet.net ([154.20.166.96]) by priv-edtnes44.telusplanet.netESMTP <20060409180340.JGHA15758.priv-edtnes44.telusplanet.net@priv-edtnaa05.telusplanet.net> for ; Sun, 9 Apr 2006 12:03:40 -0600 Received: from ensemble.local (d154-20-166-96.bchsia.telus.net [154.20.166.96])Firewall) with ESMTP id 06NR7XW3TG for ; Sun, 9 Apr 2006 12:03:39 -0600 (MDT) Received: by ensemble.local (Postfix, from userid 501) id 2E15556497C; Sun, 9 Apr 2006 11:02:29 -0700 (PDT) Date: Sun, 9 Apr 2006 11:02:29 -0700 From: Sam Roberts To: beepwg@lists.beepcore.org Subject: Re: [BEEPwg] Any thoughts on BEEP over MPI? Message-ID: <20060409180229.GA488@ensemble.local> Mail-Followup-To: beepwg@lists.beepcore.org References: <20060409010932.GA862@ensemble.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.1 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Quoting mrose@dbc.mtview.ca.us, on Sun, Apr 09, 2006 at 09:10:41AM -0700: > >I'm trying to figure out if MPI is a general enough message passing > >protocol that you could implement BEEP over it, and whether it would > >be a good idea. In particular, whether MPI could be faster than TCP. > > > >Any pointers or thoughts would be greatly appreciated. > > MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something > else? Sorry, yes, that MPI. Sam _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Sun Apr 09 14:26:44 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FSecW-0007Fe-Iv for beep-archive@lists.ietf.org; Sun, 09 Apr 2006 14:26:44 -0400 Received: from [168.143.123.173] (helo=drakken.dbc.mtview.ca.us) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSecU-0000Qv-3k for beep-archive@lists.ietf.org; Sun, 09 Apr 2006 14:26:44 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k39IPUSV027962; Sun, 9 Apr 2006 11:25:31 -0700 Received: from smtp5.suscom.net (smtp5.suscom.net [64.78.83.245]) k39IPSUm027959 for ; Sun, 9 Apr 2006 11:25:28 -0700 Received: from localhost (unknown [127.0.0.1]) by smtp5.suscom.net (Postfix) with ESMTP id 9A8535100FA; Sun, 9 Apr 2006 14:25:19 -0400 (EDT) Received: from smtp5.suscom.net ([127.0.0.1]) by localhost (smtp5 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 06044-01-32; Sun, 9 Apr 2006 14:25:17 -0400 (EDT) Received: from [127.0.0.1] (ip52.213.45.216.suscom.net [216.45.213.52]) by smtp5.suscom.net (Postfix) with SMTP id D15555100F5; Sun, 9 Apr 2006 14:25:16 -0400 (EDT) Message-ID: <4439517B.2020005@saraswat.org> Date: Sun, 09 Apr 2006 14:24:59 -0400 From: Vijay Saraswat User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Roberts Subject: Re: [BEEPwg] Any thoughts on BEEP over MPI? References: <20060409010932.GA862@ensemble.local> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new .250 at suscom.net cc: beepwg@lists.beepcore.org cc: Marshall Rose X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Marshall Rose wrote: >> I'm trying to figure out if MPI is a general enough message passing >> protocol that you could implement BEEP over it, and whether it would >> be a good idea. In particular, whether MPI could be faster than TCP. >> >> Any pointers or thoughts would be greatly appreciated. > > > MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something > else? > Very odd thought. MPI is used widely as a message-passing API (particularly w/ C,C++ and Fortran) for high performance computing HPC). The synchronous (2-way) MPI is used much more widely than the 1-way (remote memory read/write) enabled version. It supports user-space synchronous message-passing. (There is also support, using immediate/nonblocking mode for asynchronous messaging.) The bulk of MPI is oriented towards supporting collective operations (e.g. all reduce) over a group of such processes participating in point to point interactions with each other (grouped together in a communicator). Not sure this is particularly relevant for BEEP. Why would you want to do this? Perhaps what you might be after is that often HPC clusters are built over extremely high-performance interconnects that are non-IP-based. For instance, ARMCI and LAPI, based on infiniband/quadrics/myrinet/IBM Federation switches and other network I/O cards http://citeseer.ist.psu.edu/nieplocha99armci.html http://www.emsl.pnl.gov/docs/global/papers/lapi.pdf (There is also GASNet, http://gasnet.cs.berkeley.edu/) So you might consider layering on top of these. What are you really after? Best, Vijay _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Wed Apr 26 03:08:37 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYe8b-0000SV-5o for beep-archive@lists.ietf.org; Wed, 26 Apr 2006 03:08:37 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYdLR-000692-Ko for beep-archive@lists.ietf.org; Wed, 26 Apr 2006 02:17:49 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FYd6y-0001UJ-Rj for beep-archive@lists.ietf.org; Wed, 26 Apr 2006 02:02:55 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k3Q60et5018754; Tue, 25 Apr 2006 23:00:45 -0700 Received: from priv-edtnes09.telusplanet.net (outbound02.telus.net [199.185.220.221])k3Q60XDQ018750 for ; Tue, 25 Apr 2006 23:00:34 -0700 Received: from priv-edtnaa05.telusplanet.net ([154.20.166.96]) by priv-edtnes09.telusplanet.netESMTP <20060426060022.LKNZ888.priv-edtnes09.telusplanet.net@priv-edtnaa05.telusplanet.net> for ; Wed, 26 Apr 2006 00:00:22 -0600 Received: from ensemble.local (d154-20-166-96.bchsia.telus.net [154.20.166.96])Firewall) with ESMTP id 28HV6VR4KL for ; Wed, 26 Apr 2006 00:00:15 -0600 (MDT) Received: by ensemble.local (Postfix, from userid 501) id 93D50568450; Tue, 25 Apr 2006 22:59:09 -0700 (PDT) Date: Tue, 25 Apr 2006 22:59:08 -0700 From: Sam Roberts To: beepwg@lists.beepcore.org Subject: Re: [BEEPwg] Any thoughts on BEEP over MPI? Message-ID: <20060426055908.GA441@ensemble.local> Mail-Followup-To: beepwg@lists.beepcore.org References: <20060409010932.GA862@ensemble.local> <4439517B.2020005@saraswat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4439517B.2020005@saraswat.org> User-Agent: Mutt/1.5.11 X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: -2.6 (--) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Quoting vijay@saraswat.org, on Sun, Apr 09, 2006 at 02:24:59PM -0400: > Marshall Rose wrote: > > >>I'm trying to figure out if MPI is a general enough message passing > >>protocol that you could implement BEEP over it, and whether it would > >>be a good idea. In particular, whether MPI could be faster than TCP. > >> > >>Any pointers or thoughts would be greatly appreciated. > > > > > >MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something > >else? > > > Very odd thought. > > MPI is used widely as a message-passing API (particularly w/ C,C++ and > Fortran) for high performance computing HPC). The synchronous (2-way) > MPI is used much more widely than the 1-way (remote memory read/write) > enabled version. It supports user-space synchronous message-passing. > (There is also support, using immediate/nonblocking mode for > asynchronous messaging.) The bulk of MPI is oriented towards supporting > collective operations (e.g. all reduce) over a group of such processes > participating in point to point interactions with each other (grouped > together in a communicator). Not sure this is particularly relevant for > BEEP. > Why would you want to do this? Perhaps what you might be after is that > often HPC clusters are built over extremely high-performance > interconnects that are non-IP-based. For instance, ARMCI and LAPI, based > on infiniband/quadrics/myrinet/IBM Federation switches and other > network I/O cards Yes, exactly. Its not me in particular. I was making a "hallway pitch" to consider using BEEP to replace parts of the proprietary inter-machine protocols used by our application, and I got a bit of traction, but I keep hearing about a long-term goal of "using MPI because it will be faster than the TCP we currently use". > http://citeseer.ist.psu.edu/nieplocha99armci.html > http://www.emsl.pnl.gov/docs/global/papers/lapi.pdf > > (There is also GASNet, http://gasnet.cs.berkeley.edu/) > > So you might consider layering on top of these. I think there is some consideration of MPI, because its thought that it will theoretically allow us access in an API independent way to fast system interconnects. > What are you really after? I think its unlikely that MPI is a general purpose "fast" way of getting asynchronous messages between nodes, and I'd like to nip in the bud any suggestion that we can't consider BEEP because we'll be using MPI some time in the future. Or alternatively, be able to say that BEEP could run over MPI if we ever needed it to. Thanks a lot for your comments. Sam _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Fri Apr 28 11:02:32 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZUUK-0005Gu-Ou for beep-archive@lists.ietf.org; Fri, 28 Apr 2006 11:02:32 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZUUH-0006z6-CM for beep-archive@lists.ietf.org; Fri, 28 Apr 2006 11:02:32 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k3SF0gfH007967; Fri, 28 Apr 2006 08:00:52 -0700 Received: from dolphin.aspl.es (134.Red-80-34-198.staticIP.rima-tde.net [80.34.198.134])k3SF0Yl9007960; Fri, 28 Apr 2006 08:00:35 -0700 Received: from elaine ([10.0.0.4] helo=vulcan.aspl) by dolphin.aspl.es with esmtp (ASPL Mail Server XP#1) id 1FZUSB-00048m-00; Fri, 28 Apr 2006 17:00:19 +0200 From: Francis Brosnan Blazquez To: BEEPwg , BEEP Content-Type: text/plain; charset=ISO-8859-15 Organization: Advanced Software Production Line, S.L. Date: Fri, 28 Apr 2006 17:00:21 +0200 Message-Id: <1146236421.4025.6.camel@vulcan.aspl> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-Scanner: exiscan *1FZUSB-00048m-00*ZBh.RTqPLdU* X-MIME-Autoconverted: from quoted-printable to 8bit by drakken.dbc.mtview.ca.us id k3SF0Yl9007960 Subject: [BEEPwg] [ANN] Vortex Library 0.8.11 is ready! X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by drakken.dbc.mtview.ca.us id k3SF0gfH007967 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 ########################################### ## Vortex Library 0.8.11 Stable Release ## ########################################### Release note ~~~~~~~~~~~~ Advanced Software Production Line is proud to announce the Vortex Library 0.8.11 availability: an open source "BEEP Core" protocol implementation written in C, mapped onto TCP/IP. Vortex Library has been developed inside the Af-Arch project as its data transport layer. Vortex Library is a stable and robust application protocol development toolkit. Currently it is running under Microsoft Windows and GNU/Linux platforms. Check out the following links to get ready with Vortex Library: - http://vortex.aspl.es=20 [Vortex Library homepage] =20 - http://www.sf.net/projects/vortexlibrary [Sources and Win32 binaries] - http://fact.aspl.es [Af-Arch homepage where Vortex Library is being developed] - http://www.beepcore.org [BEEP Core community web site] - http://xml.aspl.es [Axl Library, XML 1.0 implementation] =20 The release in short ~~~~~~~~~~~~~~~~~~~~ A new library have been developed to disable LibXML-2.0 dependency: Axl Library. Now Vortex Library have its own XML toolkit enabling to produce better tailored XML solutions, especially, those profiles that requires XML for its function. A complete XML-RPC profile implementation have been added. Changes since 0.8.11 ~~~~~~~~~~~~~~~~~~~~ This is a short release note, for full details check:=20 http://lists.aspl.es/pipermail/vortex/2006-April/000016.html About Us ~~~~~~~~ Advanced Software Production Line is leading the Af-Arch project: a complete framework to develop distributed application to manage enterprise process. Af-Arch project relies on Vortex Library to exchange data between its distributed nodes. Advanced Software Production Line also provides GNU/Linux support and consulting services on how organization can introduce GNU/Linux inside its process, making other platforms to interact with GNU/Linux. Contact us, using English or Spanish, to get commercial support and/or BEEP based development services. You can reach us: http://www.aspl.es - info@aspl.es We hope Vortex Library help you. Enjoy Vortex Library! =20 -- Francis Brosnan Bl=E1zquez - francis@aspl.es Advanced Software Production Line - http://www.aspl.es 28th Apr 2006, Madrid (Spain) =20 _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Fri Apr 28 11:19:48 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZUl2-0001cZ-JM for beep-archive@lists.ietf.org; Fri, 28 Apr 2006 11:19:48 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZUl1-0008BF-8p for beep-archive@lists.ietf.org; Fri, 28 Apr 2006 11:19:48 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k3SFIlUI008392; Fri, 28 Apr 2006 08:18:52 -0700 Received: from [IPv6:::1] (localhost.localdomain [127.0.0.1]) k3SFHpcE008376; Fri, 28 Apr 2006 08:18:44 -0700 In-Reply-To: <1146236421.4025.6.camel@vulcan.aspl> References: <1146236421.4025.6.camel@vulcan.aspl> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9336205B-A1BE-4D20-8338-FE6E0BB4C3D2@dbc.mtview.ca.us> Content-Transfer-Encoding: 7bit From: Marshall Rose Subject: Re: [BEEPwg] [ANN] Vortex Library 0.8.11 is ready! Date: Fri, 28 Apr 2006 17:18:39 +0200 To: Francis Brosnan Blazquez X-Mailer: Apple Mail (2.749.3) cc: BEEPwg cc: BEEP X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 > Advanced Software Production Line is proud to announce the Vortex > Library 0.8.11 availability: an open source "BEEP Core" protocol > implementation written in C, mapped onto TCP/IP. congrats! /mtr _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Fri Apr 28 12:10:57 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZVYX-0001Mk-IW for beep-archive@lists.ietf.org; Fri, 28 Apr 2006 12:10:57 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZVYW-0002YF-6R for beep-archive@lists.ietf.org; Fri, 28 Apr 2006 12:10:57 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k3SG9GSG009093; Fri, 28 Apr 2006 09:09:20 -0700 Received: from dolphin.aspl.es (134.Red-80-34-198.staticIP.rima-tde.net [80.34.198.134])k3SG98kv009083; Fri, 28 Apr 2006 09:09:09 -0700 Received: from elaine ([10.0.0.4] helo=vulcan.aspl) by dolphin.aspl.es with esmtp (ASPL Mail Server XP#1) id 1FZVWV-0005bq-00; Fri, 28 Apr 2006 18:08:51 +0200 Subject: Re: [BEEPwg] [ANN] Vortex Library 0.8.11 is ready! From: Francis Brosnan Blazquez To: Marshall Rose In-Reply-To: <9336205B-A1BE-4D20-8338-FE6E0BB4C3D2@dbc.mtview.ca.us> References: <1146236421.4025.6.camel@vulcan.aspl> <9336205B-A1BE-4D20-8338-FE6E0BB4C3D2@dbc.mtview.ca.us> Content-Type: text/plain; charset=ISO-8859-15 Organization: Advanced Software Production Line, S.L. Date: Fri, 28 Apr 2006 18:08:54 +0200 Message-Id: <1146240534.4025.22.camel@vulcan.aspl> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-Scanner: exiscan *1FZVWV-0005bq-00*VPK8kInse7M* X-MIME-Autoconverted: from quoted-printable to 8bit by drakken.dbc.mtview.ca.us id k3SG98kv009083 cc: BEEPwg cc: BEEP X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by drakken.dbc.mtview.ca.us id k3SG9GSG009093 X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 El vie, 28-04-2006 a las 17:18 +0200, Marshall Rose escribi=F3: > congrats! Thanks Marshall!! >=20 > /mtr >=20 --=20 Francis Brosnan Blazquez Advanced Software Production Line, S.L. _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg