Hi Elias,
thanks, I have put Unix sockets for shared variables onto my TODO list.
It is easier to first replace the UDP sockets with TCP sockets (reducing
the total number of sockets used) and then change the socket type.
I also doubt that anybody is using shared variables at all because I haven't
received any trouble reports on them.
/// Jürgen
On 06/27/2014 06:28 PM, Elias Mårtenson wrote:
Nice! I'll try it out on Android shortly.
On Android (and other platforms as well) there is the issue of
security. One does not want other applications to be able to randomly
connect to the server. May I suggest that you add the ability to use
Unix domain sockets instead? The code to do this is almost identical
to that of TCP, and it has the advantage of being secure.
I support both TCP and Unix domain sockets in the native part of
gnu-apl-mode. You can look here ofr an example of how I do it:
https://github.com/lokedhs/gnu-apl-mode/blob/master/native/UnixSocketListener.cc#L44
Regards,
Elias
On 28 June 2014 00:06, Juergen Sauermann
<[email protected] <mailto:[email protected]>>
wrote:
Hi,
as of SVN 345 I have changed the implementation of shared
variables in GNU APL.
So far shared variables used a shared memory (aka. /dev/shm/apl-svars)
for the coordination between the different APL interpreters and APs.
This has caused problems with environments that did not provide
shared memories, in particular Javascript and Android.
>From now on the shared memory has been replaced by a memory held
in a separate process called APserver. The APL interpreters and
APs communicate
with APserver using TCP on localhost. APserver can be started
manually beforehand,
but the normal way to use it is to do nothing (and GNU APL will
fork an APserver
if none is running).
You should do a make install after your next SVN update so that
APserver gets installed.
/// Jürgen
