[zeromq-dev] Python message passing
sophacles at gmail.com
Fri Apr 24 17:38:29 CEST 2009
On Fri, Apr 24, 2009 at 8:56 AM, Martin Sustrik <sustrik at fastmq.com> wrote:
> This won't work in strongly typed languages (C,C++,Java). By coincidence
> these languages are main focus of the project :)
Yeah I suspected as much. I think this is less of a typing feature as it is
an introspection feature. Im pretty sure I could do this in Java, but it
would be a pain.
<pedantic_comment importance="feel free to ignore">
Strongly typed is different from static typed. Python is very strongly
typed, as there is no way to change the type of an object once it is
created. It is however dynamic, meaning that types are figured out at
runtime. Similarly C is static typed, but weak, as types can be cast to
other types pretty much at will, but must always be declared.
Also of relevance, strength of typing is usually seen as a relative value,
or perhaps a scale, but not a binary value.
> A tangent off of this: I've been wondering for a while why the decision
>> was made to include wrappers for certain very slow languages like python.
>> It seems to me that all the focus on efficiency and maximizing the use of a
>> big cluster, that python et al undo all of that.
> Several reasons:
> 1. Rapid prototyping.
> 2. High-perf system written primarily in C can still benefit from
> administrative components written in Python. With administration the
> performance is irrelevant. Ability to write/change code easily is much more
> important. (It would be nice to have Perl binding for exactly this reason.)
> 3. Even python can benefit from features like ability to handle thousands
> of connections at the same time, fast disk offload of messages,
> auto-reconnection as application fail and get restarted etc.
Aha, this makes sense to me now. Thinking about point 2, it also seems to me
there could be information sources to the high perf system that also don't
need the speed, but should interface with it (parts of the application
proper, not just admin).
Thanks for the explaination.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the zeromq-dev