qnx4 SRR <-> perl5 interface

QNX Newsgroups (Archives) comp.os.qnx
#1

hi all

we need to access some qnx4 native server wich originally interracts with
clients through send/receive/reply interface from perl 5.005 script. i see
three variants:

  1. write some perl/c library (through ux interface ?) in order to call
    send/receive/reply directly from perl script. this would be perfect for us.
    the question is how ? i didn’t found any information about it in the perl5
    documentation from qnx/usr/free distributives.

  2. write some external programm i.e. bridge between server and perl script
    in order to send requests to server and get result with help of this
    programm. write request from perl script to stdin of bridge and read the
    result from strout. well, it seems to be quite easy, but the performance of
    this bridge is seems to be unsutable :frowning:

  3. write additional tcp/ip interface on the server side and access server
    through sockets. well, it seems to be slightly better, but much more
    complicated to implement our api with tcp/ip + there are ten diffirent
    servers so it’s time coslty to write tcp/ip wrapper for each of them.

any ideas ?

–

Thanks for your attention,
Ian M. Zagorskih, Software Developer, Novosoft Ltd.
E-Mail: ianzag@pochta.net ICQ 28632525
Web: http://www.novosoft.ru

// wbr

#2

In article <8l1c1r$2sre$1@nl.novosoft.ru>, "ian says…

hi all

we need to access some qnx4 native server wich originally interracts with
clients through send/receive/reply interface from perl 5.005 script. i see
three variants:

  1. write some perl/c library (through ux interface ?) in order to call
    send/receive/reply directly from perl script. this would be perfect for us.
    the question is how ? i didn’t found any information about it in the perl5
    documentation from qnx/usr/free distributives.

  2. write some external programm i.e. bridge between server and perl script
    in order to send requests to server and get result with help of this
    programm. write request from perl script to stdin of bridge and read the
    result from strout. well, it seems to be quite easy, but the performance of
    this bridge is seems to be unsutable > :frowning:

  3. write additional tcp/ip interface on the server side and access server
    through sockets. well, it seems to be slightly better, but much more
    complicated to implement our api with tcp/ip + there are ten diffirent
    servers so it’s time coslty to write tcp/ip wrapper for each of them.

any ideas ?

Use Python for QNX4 :wink: … it supports all what you want: Socket interface,
QNX SRR, CORBA, Pyro, gdbm, Berkeley database lib 1.86 … interfaces for
GUI 's (qt,Tilcon) …

Regards

Armin

#3

On the QNX site (look in free software), there is a Perl module that
implements extentions to perl (using X-Subs) allowing perl scripts to use
QNX inter-task communication mecanisms. You can integrate it to your
version of Perl and there you go.

Also note that I worked with the original author of that module to add a few
new function inside that module for other QNX specific stuff. I’m not sure
if the author released this new version (0.04) yet. (look for it in CPAN as
well). If you’re interrested I can give you it’s address so you can get a
copy if Version 0.03 is not enough.

“ian zagorskih” <ianzag@mail.ru> wrote in message
news:8l1c1r$2sre$1@nl.novosoft.ru…

hi all

we need to access some qnx4 native server wich originally interracts with
clients through send/receive/reply interface from perl 5.005 script. i see
three variants:

  1. write some perl/c library (through ux interface ?) in order to call
    send/receive/reply directly from perl script. this would be perfect for
    us.
    the question is how ? i didn’t found any information about it in the perl5
    documentation from qnx/usr/free distributives.

  2. write some external programm i.e. bridge between server and perl script
    in order to send requests to server and get result with help of this
    programm. write request from perl script to stdin of bridge and read the
    result from strout. well, it seems to be quite easy, but the performance
    of
    this bridge is seems to be unsutable > :frowning:

  3. write additional tcp/ip interface on the server side and access server
    through sockets. well, it seems to be slightly better, but much more
    complicated to implement our api with tcp/ip + there are ten diffirent
    servers so it’s time coslty to write tcp/ip wrapper for each of them.

any ideas ?

–

Thanks for your attention,
Ian M. Zagorskih, Software Developer, Novosoft Ltd.
E-Mail: > ianzag@pochta.net > ICQ 28632525
Web: > http://www.novosoft.ru

// wbr