[zeromq-dev] ooc bindings for ØMQ

[gonzalo diethelm]

> You saw http://www.zeromq.org/blog:multithreading-magic?

Yes. As it is usually the case for me when reading docs in 0MQ's site, I contemplate them with a rightful sense of "I am home at last".

> > Completely agree. The strength in this department lies in
> > having such a light-weight protocol definition that easily
> > bends to become anything one could possibly need.
> 
> While this is out of scope for 0MQ core, it makes sense to solve this
> problem in such a way that 0MQ users do not have to reinvent the wheel
> each time.  It's impossible to connect different languages without
> some agreed data representation layer and the existing ones all seem
> rather... heavy.

For my use case, I disagree. I am currently using Google's Protocol Buffers; I could easily switch to CDR / XDR / whatchamacallit...

Now, if you truly want to define 0MQ as a standard way of communicating across applications / languages / Oss, then yes, you need to standardize the data representation. I personally believe this road leads to madness.

> Perhaps time to start looking at what such a data representation layer
> should look like.  We made some nice ones for AMQP but the challenge
> seems to be to avoid representing every possible datatype (at some
> point AMQP got multiple ways to represent bits...).
> 
> If anyone wants to pull down the AMQP/0.8 spec and look at the data
> representation parts, and give an opinion, that might be a place to
> start.  I'm happy to throw up a straw man RFC if that helps the
> discussion.

You are certainly more knowledgeable in this department, and I will be interested in seeing any proposals you put forward.

> > Again, completely agree. I have never understood why
> > it was necessary to invent XML when we have had
> > S-expression for what, half a century now?
> 
> S-expression was too simple and would never have spawned an entire
> industry of experts :-).

You got that right.

> Seriously, though, I think XML came from a
> more formal document processing environment (SGML) that fit the web
> better than S-expression.

I understand what you are saying, but can only retort... whatever. In fact, I must admit to something: my secret atomic weapon for software development is... Scheme. I have long held the opinion that you could use Scheme (and S-expressions) to develop everything in a multi-tiered, multi-processing, multi-threading, multi-whatever, application: HTML, JavaScript, CSS, web layer, business logic, data logic, SQL, the data itself, EVERYTHING can be modeled using Scheme and dynamically generating whatever you need.

Scheme (or Lisp) is the end-all of languages. But I will shut up for now, before anyone here considers me mad... I must take my medication now ;-)

> > Again, to state it explicitly: thanks to the team for creating
> > 0MQ. It fits perfectly into my infrastructure box.
> 
> Thanks to Martin Sustrik for pulling it all together, he is a genius
> at Keeping it Simple (and Making it Fast).

Exactly. Cheers!

-- 
Gonzalo Diethelm

----------------------------------------- 
Declaración de confidencialidad: Este Mensaje esta destinado para
el uso de la o las personas o entidades a quien ha sido dirigido y
puede contener información reservada y confidencial que no puede
ser divulgada, difundida, ni aprovechada en forma alguna. El uso no
autorizado de la información contenida en este correo podrá ser
sancionado de conformidad con la ley chilena. 
Si usted ha recibido este correo electrónico por error, le pedimos
eliminarlo junto con los archivos adjuntos y avisar inmediatamente
al remitente, respondiendo este mensaje. 

"Before printing this e-mail think if is really necesary".
Disclosure: This Message is to be used by the individual,
individuals or entities that it is addressed to and may include
private and confidential information that may not be disclosed,
made public nor used in any way at all. Unauthorized use of the
information in this electronic mail message may be subject to the
penalties set forth by Chilean law. 
If you have received this electronic mail message in error, we ask
you to destroy the message and its attached file(s) and to
immediately notify the sender by answering this message.