Carl Trieloff wrote:
Gary Matulis wrote:
Hi Carl, Steve -
I would say I'm fairly ambitious. I expect to have a significant
amount of
time over the next couple of months to dedicate to the work. I don't
have a
particular area of interest within Qpid (other than within the C++
code) as
I'm just beginning to study the project. So, I'm open to suggestions
about
what area to work in, or what area needed help. As for platforms, I
could
do either Linux or Windows, but I'm much more familiar with the Linux
toolchain.
- Gary
My list of top bigger items is:
- GSSAPI kerberos authentication SASL (short term, have need for this
soon) (have SASL, need to make sure kerb works)
We have cyrus-sasl integration on the broker side, but not yet on the
client side (QPID-976).
- GSSAPI kerberos encryption (short term, have need for this soon)
- Priority message queues (I think someone is looking into this one)
QPID-529, I believe Danushka is working on this (he didn't show up in
the list of valid assignment targets; can only committers have jiras
assigned to them?)
- Performance work (If you are interested, I can direct you at the data
I have seen so far on the hots spots from systemtap/oprofile)
- Currently there is a message store here:
https://svn.jboss.org/repos/rhmessaging/store/trunk/cpp which can't
live in qpid
as if uses some non ASL licensed dependencies. It also uses Linux
specific AIO. It would be great to get a ASL license-able
store module added to the project
Manuel was also going to start work on an ODBC version of this
(http://www.nabble.com/Two-Phase-Commit-and-qpid-td19665777.html).
- Hooking in additional instrumentation data QMF
- mapping AMQP wiring commands into QMF
- well I think there is quite a bit that can be done on QMF if you are
interested in this area...
- I am sure Steve has Windows related stuff that needs doing.
Another option:
* selectors (JMS style expression indicating which messages are of
interest) (QPID-530)
