-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACE dev_poll reactor for usage in TAO #2048
Comments
dev poll is still experimental for TAO, not recommended for production usage in TAO. See https://github.com/DOCGroup/ACE_TAO/wiki/ACE-and-TAO-Commercial-support for support, making dev poll fit for production in TAO is something that has to be funded by someone (or someone has to do the hard work). |
See also #2045 and the old bugzilla http://bugzilla.dre.vanderbilt.edu/ |
If we are going with commercial support. How long do you foresee supporting this functionality for production use and if you can give some indication on commercial or pricing, it will help us to take a decision. |
For commercial support please contact us directly ([email protected]) or one of the other support companies. |
Altough anecdotical, we have been testing the devpoll reactor without problems if we don't use SSL |
We are using ACE/TAO FOSS 3PP for exposing the CORBA communication and currently we are using the default ORBReactorType i.e., tp (ACE_TP_Reactor).
Tp Reactor type is using the “select()” API which has the limitation on monitoring and supports file descriptor number less than 1024 only. As per the TAO documentation we have seen an another ORBReactorType “dev_poll” which doesn’t have the limitations like “tp” reactor, also “depv_poll” is supported on Linux based platforms as an experimental functionality.
Does experimental functionality is recommended by community to use for production deployments? If yes, will it be supported if there is any issue occurs? If not, can we know their release plans to deliver it for production use cases.
The text was updated successfully, but these errors were encountered: