Hello there!
Thanks for the answers, it works now.
It was a bit unclear to me that having 1 instance of GIST and 1 instance of my NSLP code needs 2 api-s for different nslp-ids, but only for reception. As I believe it now, you wrote GIST mainly with having 1 nslp-id per NSLP-application code in mind.
What it needed was two separate api instances, with same callbacks registered, but different nslp-ids. Then I issue 2 api->waitforsignal calls (for both pointers), and receive messages correctly with both nslp-ids.
However, I use only one api for the sendmessage call, I just alter the nslp-id of the message. This is not nice , but it just works.
So finally, I believe this is the way.
Thanks again,
Ferenc
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hi Ferenc,
please read inline.
It was a bit unclear to me that having 1 instance of GIST and 1 instance of my NSLP code needs 2 api-s for different nslp-ids, but only for reception. As I
The socket descriptor of the unix-socket registered in GIST is tight to one NSLP-ID. At the moment you can't register another NSLP-ID having the same socket desciptor.
believe it now, you wrote GIST mainly with having 1 nslp-id per NSLP-application code in mind.
This is true. We didn't have this case before.
What it needed was two separate api instances, with same callbacks registered, but different nslp-ids. Then I issue 2 api->waitforsignal calls (for both pointers), and receive messages correctly with both nslp-ids.
You can register the same callback functions with the second instance, if there's no difference in handling.
However, I use only one api for the sendmessage call, I just alter the nslp-id of the message. This is not nice , but it just works.
It should also work using the 2 instances of NslpApi for SendMessage()
api1->SendMessage(...); api2->SendMessage(...);
Bernd
nsis_imp@informatik.uni-goettingen.de