Re: Moving QMF to a top-level directory

Robert Godfrey wrote: 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

Re: Moving QMF to a top-level directory

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/

Re: Moving QMF to a top-level directory

>> >> 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      

Re: Moving QMF to a top-level directory

On Thu, 2009-05-07 at 12:21 -0400, Ted Ross wrote: > ... > It may be that QMF will someday become its own project or sub-project if > interest continues to increase. This separation will make an eventual > spin-off much easier. I can't see how this makes sense, at least presently: The qpid C++

Re: Moving QMF to a top-level directory

Rafael Schloming wrote: Ted Ross wrote: Rafael Schloming 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

Re: Moving QMF to a top-level directory

Hi Marnie, QMF evolved from what was originally a mechanism to manage the c++ broker. It is now a much more general-purpose facility for managing just about anything. There is a growing community of users forming around QMF including some developers who are submitting patches. I'm not sure

Re: Moving QMF to a top-level directory

Ted Ross wrote: Rafael Schloming 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 qp

Re: Moving QMF to a top-level directory

Hi Ted, Why do you need/want separation - what is the goal for moving QMF around ? It'd be useful to understand the technical drivers for making changes to the codebase/structure. Thanks & Regards, Marnie On Thu, May 7, 2009 at 3:45 PM, Ted Ross wrote: > Rafael Schloming wrote: > >> Ted Ross w

Re: Moving QMF to a top-level directory

Rafael Schloming 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

Re: Moving QMF to a top-level directory

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 module

Re: Moving QMF to a top-level directory

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

Re: Moving QMF to a top-level directory

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 module

Re: Moving QMF to a top-level directory

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/

Re: Moving QMF to a top-level directory

It might be good to put the before and after structure into the mail thread Carl. Ted Ross wrote: QMF (the Qpid Management Framework) is a set of libraries and components layered over Qpid messaging for remote object management. The QMF code (used to manage the c++ broker) is currently in

Moving QMF to a top-level directory

QMF (the Qpid Management Framework) is a set of libraries and components layered over Qpid messaging for remote object management. The QMF code (used to manage the c++ broker) is currently in the same directories as the broker and clients (i.e. qpid/cpp/src/qpid, python, ruby/lib, etc.). Ther