Hi PJ,
On Sun, Mar 6, 2011 at 10:34 PM, PJ Durai wrote:
> Greetings,
>
> I am having some issues in building my application in Suse 11.3 instalation.
>
> Zero MQ library itself has no problems building.
>
> But when I build my application, I end up with the following error
>
> /home/pi/dev/lib/li
Greetings,
I am having some issues in building my application in Suse 11.3 instalation.
Zero MQ library itself has no problems building.
But when I build my application, I end up with the following error
/home/pi/dev/lib/libzmq.a(libzmq_la-uuid.o): In function `uuid_t':
/home/pi/tmp/zeromq-2.1.
woot!
zeromq team++
--d
2011/3/6 Pieter Hintjens :
> Hi all,
>
> We're pleased to announce that 0MQ stable release 2.1 (v2.1.2, rc2)
> has been released and is available for download at:
>
> * http://download.zeromq.org/zeromq-2.1.2.tar.gz (UNIX line endings)
> * http://download.zeromq.org/zeromq
On 6 March 2011 17:36, Pieter Hintjens wrote:
> This 2.1 release candidate is considered highly stable especially over
> 2.0.10. We recommend you use this release for all 0MQ projects where
> possible. It fixes several memory leaks since rc1, and OpenPGM should
> be working properly again.
>
>
I'
On 7 March 2011 01:31, Alex Forster wrote:
> Steven McCoy miru.hk> writes:
>
> > Clean builds under Win64.
> > ...
> > Improve spinlock performance with inline ticket based spinlock
> implementation.
>
>
> http://www.google.com/search?q=__asm+keyword+not+supported+on+this+architecture
>
> ticket
On Sun, Mar 6, 2011 at 9:17 PM, MinRK wrote:
> Thanks, I think that makes sense. It's mainly the 'stable beta release' that
> caused problems. The small change to the download page is perfect.
OK, great.
> I think it is a good idea to push people to test the new software, but
> being ambiguou
Sorry, forgot to reply to the list...
-- Forwarded message --
From: Pieter Hintjens
Date: Sun, Mar 6, 2011 at 8:40 PM
Subject: Re: [zeromq-dev] 0MQ stable release 2.1 (v2.1.2, rc2) released
To: MinRK
On Sun, Mar 6, 2011 at 8:15 PM, MinRK wrote:
> I do have a question about t
This is great, it looks like the new repo organization is having the
desired effect!
I do have a question about the use of version numbers and release
candidates. The
traditional model for beta/rc is that they represent an unfinished
revision to a given version,
i.e. 2.1.1-beta will become 2.1.1-
On Sun, Mar 6, 2011 at 6:01 PM, Martin Sustrik wrote:
> Also, it would be helpful to expand the text. Say: "Implement a delivery
> mechanism that can withstand restarts of both the sender and receiver,"
> doesn't make much sense for me.
Seems clear enough. This particular functionality is almost
Steven McCoy miru.hk> writes:
> Clean builds under Win64.
> ...
> Improve spinlock performance with inline ticket based spinlock implementation.
http://www.google.com/search?q=__asm+keyword+not+supported+on+this+architecture
ticket.h is coughing up because Visual C++ doesn't support inline asse
Hi all,
The page listing the ideas for GSoC looks like a feature wishlist at the
moment.
Can the authors please reexamine the list and check whether the items
are actually doable by a studing during the summer? I think that say
implementing XA distributed transactions are far beyond the scope.
Hi Yin,
First of all, you should be aware that organisations participating in
GSoC are to be approved on March 18th. So, 0MQ may or may not be
approved. Still, you are free to contribute to 0MQ in either case.
> I am a CS master student from China, and got interested in some of
> your listed Su
On Sun, Mar 6, 2011 at 5:12 PM, Han Holl wrote:
> It's an almost literal copy from the guide:
> // Send reply back to client
> zmq::message_t reply (6);
> memcpy ((void *) reply.data (), "World", 5);
> socket.send (reply);
Yes, the C++ code had an error (fixed now).
On 03/06/2011 05:12 PM, Han Holl wrote:
> zmq::message_t reply (3);
> memcpy ((void *) reply.data (), "OK", 2);
> socket.send (reply);
It's definitely an error. The third byte is un-initialiased, so it's not
even guaranteed to be zero.
Martin
_
On Sunday, March 06, 2011, Pieter Hintjens wrote:
> On Sun, Mar 6, 2011 at 12:21 PM, Mikko Koppanen
>
> wrote:
> > as the message data is an opaque binary blob I am not sure whether
> > removing the trailing \0 is correct behaviour. If you are receiving a
> > message with a trailing \0 it means t
On Sun, Mar 6, 2011 at 12:21 PM, Mikko Koppanen
wrote:
> as the message data is an opaque binary blob I am not sure whether
> removing the trailing \0 is correct behaviour. If you are receiving a
> message with a trailing \0 it means that the sender has included it as
> a part of the message.
In
On Sat, Mar 5, 2011 at 8:49 PM, Han Holl wrote:
>
> Hi,
>
> The function
> s.recv
> returns a string like "OK\000", at least with my ruby-1.8.7.334-1.fc14.x86_64.
> Maybe there are ruby implementations that make the trailing zero go away.
Hi,
as the message data is an opaque binary blob I am not
Hi all,
We're pleased to announce that 0MQ stable release 2.1 (v2.1.2, rc2)
has been released and is available for download at:
* http://download.zeromq.org/zeromq-2.1.2.tar.gz (UNIX line endings)
* http://download.zeromq.org/zeromq-2.1.2.zip (Windows line endings)
This 2.1 release candidate is
18 matches
Mail list logo
