Re: [FORGE] updating sockets

[Paul Dreik]

On 2014-12-03 16:24, Juan Pablo Carbajal wrote:
> Hi all,
> 
> I guess is time to release a new sockets package, even if only to
> remove the deprecation warning.
> 
> Since a while I am trying to get something nice working to connect
> Octave and Python. I found ØMQ [1] and I thought we should pimp up the
> socket package to use ØMQ + some package creator (I am looking at JSON
> and MSGPACK).
> 
> What do you think of this?
> Do you see any problems (like license issues, etc... it shouldn't ØMQ is LGPL)
> Do you have suggestions?
> 

Hi!
It has been a while since I touched the sockets package. In this case,
"no news is good news".

1)
what do you mean by deprecation warning? it still builds and works fine,
as far as I know? The only open bug I can find is #111 which is related
to mingw. (See point 3 for more on that topic)

2)
ØMQ may be a splendid piece of software, but please create a separate
package for it. The sockets package should be used for sockets. Other
packages can depend on it, if they need sockets and can use them from
octave rather than c++.

3)
Carne prepared for a sockets 1.2.0 release almost a year ago. I have
polished a bit on the news, and I think it is fit for release.
Unfortunately I currently do not have easy access to windows. Is it
possible to run the windows release under wine, to be able to test? Or
is there some other octave developer who wants to volunteer trying on
windows (especially mingw)?

With that said, I just pushed 1.2.0 to sourceforge. Please find a
tarball attached to this mail.

Paul

sockets-1.2.0.tar.gz
Description: application/gzip