I've only just come across this, after using clrzmq in the past.
A couple of things needed updating (which you've probably already done,
bearing in mind your post is nearly a year old):-
All socket types can either Bind() or Connect().
You limit some of your sockets to doing one or the other,
1. Ensure the DLL has permissions to run on your local machines ( right
click properties) . This is not just for .net but exes also.
2. Make sure you are running in full trust .
Regards,
Ben
On Wed, May 2, 2012 at 1:18 PM, Thomas Fee angry...@hotmail.com wrote:
Hey Alex, sounds great but no
Hey Alex, sounds great but no way I can get it to work. It's probably because
I'm a newb at this C# stuff. Would appreciate a quick look at this, a cut and
paste of your code into a program shell. At this point, I'm just trying to
get
it to compile, never mind have it work.
What I did was
On 12/21/2010 07:57 PM, Alex Forster wrote:
For example, the names of inproc endpoints are stored in the
context. If library A uses inproc endpoint named X and library B
accidentally uses endpoint X as well, they start messining with
each other.
That's a very good point, I'll definitely have
Hi Alex,
I have quite a few gripes with clrzmq and clrzmq2, and NZMQ is
incomplete in several areas, so over a few weekends this past month I've
written a new C# API for ZeroMQ based on the 2.0.10 release of zmq.h.
Great! I would suggest adding a link to your project to www.zeromq.org.
It's
Great job Alex, your implementation is very clean and simple, I liked it.
Vinicius Chiele
2010/12/21 Alex Forster a...@alexforster.com
I have quite a few gripes with clrzmq and clrzmq2, and NZMQ is incomplete
in several areas, so over a few weekends this past month I've written a new
C# API
Great! I would suggest adding a link to your project to www.zeromq.org. It's
wiki, so you can do so yourself.
Gladly, done.
I am not familiar with CLR. Doesn't the problem the context is solving (i.e.
zeromq being used from two libraries that are later on linked into a single
application
On 12/21/2010 07:07 PM, Alex Forster wrote:
I am not familiar with CLR. Doesn't the problem the context is
solving (i.e. zeromq being used from two libraries that are later
on linked into a single application and step on each other toes)
occur with .NET as well?
That is a very good question
I'm the primary author and maintainer of clrzmq2, it monitor for issue
and will endeavour to resolve them when they arise. I monitor the
mailing list and drop into #zeromq now and then.
I notice NUZQ seems to use lambdas, these were introduced in .NET 3.0, I
purposely kept clrzmq2 targeting .net
For example, the names of inproc endpoints are stored in the context. If
library A uses inproc endpoint named X and library B accidentally uses
endpoint X as well, they start messining with each other.
That's a very good point, I'll definitely have to address that. I'm willing to
jump
You do know that clrzmq2 supported all of what you mentioned besides the
reference counting.
If you had of submitted a patch for clrzmq2 it would have been very
welcome.
On Tue, 2010-12-21 at 09:00 -0200, Vinicius Chiele wrote:
Great job Alex, your implementation is very clean and simple, I
You do know that clrzmq2 supported all of what you mentioned besides the
reference counting.
If you had of submitted a patch for clrzmq2 it would have been very
welcome.
I certainly didn't mean to offend. I'll admit that, while I did have some
different ideas as to what a C#-ified ZeroMQ
I notice NUZQ seems to use lambdas, these were introduced in .NET 3.0, I
purposely kept clrzmq2 targeting .net 2.0.
The fact is a 2.0 is the prevalent .NET framework, many large
organization will actually only be using that.
The application I maintain as a day job is targeted at 2.0 and
I have quite a few gripes with clrzmq and clrzmq2, and NZMQ is incomplete in
several areas, so over a few weekends this past month I've written a new C# API
for ZeroMQ based on the 2.0.10 release of zmq.h.
ZeroMQ Interop v0.8.190.10354 (beta)
http://zeromq.codeplex.com
* Feature-complete
* MIT
14 matches
Mail list logo
