This page last changed on Feb 22, 2009 by cctrieloff.

Best way to get involved is mail dev@qpid.apache.org and say, "want to help, and state your interests"

Want needs to get done (the short term/ short list)

Theme Item component who
Performance      
  increase fanout performance c++  
  increase per-connection throughput c++  
  Shared memory transport c++  
Broker 'model'      
  Selectors c++  
  queue policies **1 c++  
  Priorities c++  
  PB exchange c++  
Security      
  SASL authentication (kerb) python  
  SASL authentication (kerb) java  
  SASL encryption (kerb) python  
  SASL encryption (kerb) java  
  SASL encryption (kerb) .net  
  SASL encryption & authentication inter broker links  
  Tests for federation and clustering with all transport and security options c++  
  SELinux ACL delegation c++  
Clustering      
  Session resume across all client  
  Processing updates to known broker urls python and ruby  
  auto detect restart durable stores for cluster c++  
Management      
  more stats (e.g. avg/min/max queue 'latencies') c++  
  configurable alerts for e.g. hitting preset queue limits c++  
  more flexible logging (more useful to end user) c++  
  QMF agents for missing clients java, python, .net  
  QMF console API for .net  
  JMX -> QMF bridge java  
  qpid-queue-tool python  
Builds      
  c++ on windows (per steve) c++  
  complete solaris c++  
  default IO for other OS's ? c++  
Future Proofing      
  High level API design work All client  
  ABI computability strategy c++  
  .Net test coverage and API review (WCF/QMF) .net  
Interop      
  0-10 for Java broker java  
  Updated IO layer for Java broker java  
Miscellaneous      
  test card iwarp support for RDMA c++  
  ASL licensed RDMS DB store c++  

**1

  • allow for killing (slow) consumer, rather than producer – python cmd line tool?
  • dequeue when all current browsers have received message (more efficient topic, also represents a step towards 1.0 model)

Target Features/work areas for Qpid 0.5

  • Kerberos Auth and encryption from all clients – in progress
  • A-A Cluster support from all clients
  • RT JVM Thread support for Java — done
  • DR links for stand-alone and clustered brokers — done
  • Producer side flow control — done
  • Updated IO layer for Java
  • Shared memory transport
  • .NET test coverage
  • Windows client build from cmd line.
  • AMQP-MGMT to WS-DM and JMX bridge committed (QMan) – mostly done
  • IP address /Hostname access control to virtualhosts (Java broker)

scratch list of stuff to help with

You can also look in JIRA under the starter section.

Here are some additional things... The following are nice task to pick up for new committers, (Please mail the list if you have interest in doing any of these)

  • Creation of Perl Client — Nice task to start on
  • Integrating AMQP-MGMT into the Java broker
  • Writing examples and getting started pages — Nice task to start on
  • Help update this site — Nice task to start on
  • Profiling for performance improvements
  • Spring integration
  • JCA / App server integrations
  • C++ broker
    • Message Priority
    • Selectors
    • Lock Free queue implementation
  • Java broker
    • Transparent 0.8/0.9/.10 support in the Java broker
    • Add Flow To Disk
    • Message Federation for Java (Fan out & forward to remote queue) – look at C++ broker and impl in Java (might need to wait for 0-10 (M4))
    • Flow control - throttling of overactive producers – might need 0-10 (M4)
Document generated by Confluence on May 26, 2010 10:33