[zeromq-dev] Costs of creating sockets?

[Ilja Golshtein]

Martin,

is the fact  "Connecting it actually creates the connection"
unavoidable even for inproc?

My question is if we are going to see the same design (TCP socket per every inproc)
in future 0mq versions or it is a subject to change.


Honestly I don't know if it is a real issue.
It makes some application design patterns (like socket per object) impossible.
Which may be not too bad ;)

Thanks.

01.10.10, 10:20, "Martin Sustrik" <sustrik at 250bpm.com>:

> Hi Ralf,
>  
>  > So how expensive is it to create (and then destroy) many sockets and
>  > connect them to the exception handling one?
>  
>  Creating socket is cheap. Connecting it actually creates the connection, 
>  which is more or less as expensive as creating the underlying connection 
>  (TCP connection in this case).
>  
>  > When is a connection
>  > actually opened?
>  
>  When zmq_connect is called, but in async manner.
>  
>  > Does a
>  > context pool connections so if sending sockets are created on the same
>  > context they can reuse the same connection?
>  
>  No.
>  
>  Martin
>  _______________________________________________
>  zeromq-dev mailing list
>  zeromq-dev at lists.zeromq.org
>  http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>  
>  

-- 
Best regards,
Ilja Golshtein.