incubator-wadi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianni Scenini <gianni.scen...@gmail.com>
Subject Re: [wadi-dev] Destination maps to Node or Service....
Date Thu, 02 Feb 2006 17:00:23 GMT
See inline comment
-G

On 2/2/06, Jules Gosnell <jules@coredevelopers.net> wrote:
> Gianny,
>
> I decided that this was of wider interest so have posted Geronimo dev
> about it.
>
> For WADI, although you convinced me to raise the level of abstraction
> above a JMS Destination, after further thought, I think we can raise the
> level of abstraction from Node to Service without having to change the
> API - Cluster and Destination are already abstract enough to express
> this stuff... - see my posting on g-dev where I suggest that we allow
> multiplexed connections etc...
>
> If, as far as WADI is concerned, we go this route (I haven't thought
> about it deeply yet, so there may be semantic issues that are not easily
> resolved), then I still don't see a good reason for losing the
> dependency on javax.jms.Destination - other than its pulling in the
> whole JMS api as a dependency, which AC and AMQ will do anyway....

I really do not see a good reason for keeping that dependency.
I might seem too pragmatic but that dependency is to me a design mistake


>
> What do you think ? Can you still make good technical case against the
> use of Destination in WADI code ? If you just replace it with another
> Abstraction (e.g. Address or RemoteService etc...), what have we gained ?
>
> Over to you :-)
>
>
> Jules
>
>
> --
> "Open Source is a self-assembling organism. You dangle a piece of
> string into a super-saturated solution and a whole operating-system
> crystallises out around it."
>
> /**********************************
>  * Jules Gosnell
>  * Partner
>  * Core Developers Network (Europe)
>  *
>  *    www.coredevelopers.net
>  *
>  * Open Source Training & Support.
>  **********************************/
>
>

Mime
View raw message