[
https://issues.apache.org/jira/browse/QPID-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805652#action_12805652
]
Ian Main commented on QPID-1982:
--------------------------------
Using a file descriptor also allows QMF to incorporate itself into other
mainloop providors, such as GTK/gnome. In a GTK/gnome app, GTK expects to have
you sitting in its main loop waiting for events. Using an FD allows us to add
another fd to that mainloop and receive callbacks when it becomes ready for
reading. Also, gtk/gnome do this and do it on windows as well so I'm sure it's
possible. We might need a portability layer there however.
> QMF ResilientConnection notifyFd feature portability
> ----------------------------------------------------
>
> Key: QPID-1982
> URL: https://issues.apache.org/jira/browse/QPID-1982
> Project: Qpid
> Issue Type: Improvement
> Components: Qpid Managment Framework
> Affects Versions: 0.5
> Environment: Windows
> Reporter: Steve Huston
>
> The QMF's C++ qmfcommon ResilientConnection class has a setNotifyFd (int fd)
> method. The docs say this can receive a file descriptor that is written on
> when certain events take place, supposedly so the other end of the channel
> can listen, select, etc. and be notified of some event.
> This construct isn't portable, both because of the datatype of the fd (int is
> not necessarily a legit handle type everywhere) and because the code assumes
> a write() will work. The code can be abstracted out to get rid of the write()
> easily enough, but what is the usage for this facility? There are no calls to
> setNotifyFd() that I can find outside of the library containing the
> implementation. So I can't tell if this is something that can be replaced by
> qpid::sys::PollableCondition or not.
> What is the use case for this, and how can we make this portable? Different
> IPC type? Callback to some private hook?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
