[Ace-users] Re: [tao-users] Notification Service with BiDir policy?

[Johnny Willemsen]

Hi Hans,

Thanks for using the PRF form. I think there is not a default option for
this, the RTEC does deliver this kind of option, maybe you can create a
patch to add such an option to the notification service.

Regards,

Johnny Willemsen
Remedy IT
Postbus 101
2650 AC  Berkel en Rodenrijs
The Netherlands
www.theaceorb.nl / www.remedy.nl  

*** Integrated compile and test statistics see
http://scoreboard.theaceorb.nl ***
*** Commercial service and support for ACE/TAO/CIAO             ***
*** See http://www.theaceorb.nl/en/support.html                 *** 

>       TAO VERSION: 1.5.8
>       ACE VERSION: 5.5.8
> 
>       HOST MACHINE and OPERATING SYSTEM: Linux
> 
>       THE $ACE_ROOT/ace/config.h FILE: config-linux.h
> 
>       THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE:
> platform_linux.GNU
> 
>       AREA/CLASS/EXAMPLE AFFECTED: Notification Service
> 
>       DOES THE PROBLEM AFFECT:
>           EXECUTION
> 
>       SYNOPSIS:
> 
> Is there an easy way of having the notification service using a 
> bidir-giop policy for communication with notification service 
> consumers/suppliers (admins/proxies)?
> 
>      DESCRIPTION:
> 
> The notification service uses a client-provided call-back to 
> push events 
> and send subscription/offer updates. This by default requires to 
> initiate a connection from the notification service to the consumer, 
> which of course does not work out of the box with NaT or 
> firewalls. The 
> BiDir policy would allow to circumvent this problem, by using the 
> client-established connection for the callback, right?
> 
> Or is there another recommended solution within the scope of 
> the CORBA 
> standard?
> 
> Cheers,
> Hans
> 
> _______________________________________________
> tao-users mailing list
> tao-users at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/tao-users
>