qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Kearney <bkear...@redhat.com>
Subject Re: Moving QMF to a top-level directory
Date Mon, 11 May 2009 09:31:37 GMT
Ted Ross wrote:
> Carl Trieloff wrote:
>> Ted Ross wrote:
>>> Good idea Carl,
>>>
>>> Here's the current structure:
>>>
>>>  qpid/cpp/src/qpid/agent      - C++ agent library
>>>  qpid/cpp/src/qpid/console    - C++ console library
>>>  qpid/cpp/src/qpid/management - Common files and components for 
>>> managing the broker
>>>  qpid/python/qmf              - Python modules
>>>  qpid/ruby/lib/qpid/qmf.rb    - Ruby console module
>>>  qpid/cpp/managementgen       - Code generation tool for C++ agent
>>>  qpid/java/management/client/src/main/java/org/apache/qpid/management  
>>> - QMF to JMX (QMan)
>>>
>>> Here's the proposed structure:
>>>
>>>  qpid/qmf/cpp           - C++ implementation of qmf components
>>>  qpid/qmf/cpp/bindings  - Wrapped bindings to components (Python, 
>>> Ruby, C#, WCF, etc.)
>>>  qpid/qmf/python        - Pure Python implementations (for portability)
>>>  qpid/qmf/java          - Pure Java implementations
>>>  qpid/qmf/windows       - Windows implementations
>>>  qpid/qmf/tools         - CLI utilities, code generators, etc.
>>>  qpid/qmf/docs          - Documentation 
>>
>> why do we need
>>
>> qpid/qmf/windows       - Windows implementations
>>
>> that should be hidden under a sys directory under

I have a pure C# console ready about ready to post. If we could keep 
qpid/qmf/dotnet or qpid/qmf/chsharp.

-- bk


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message