XMS Licensing

[alvaro]

Hi,
i'm curious about XMS, it looks like it is required for building the
SAM extension, is that right?
What sort of license is XMS released under? It wasn't very clear on the
XMS readme filed, it just said "Licensed Materials - Property of IBM"
Is there anyway to bundle the XMS code inside of the SAM source?
Registering with IBM and installing the XMS code was a bit of nuisance.

I've emailed you before (alv...@epliant.com), i've been very busy, but
i'm interested on adding support for the OpenWire protocol (native to
ActiveMQ). I would also like to create RPMs for Red Hat boxes.

Thanks,
Alvaro

[D.S.R...@googlemail.com]

Hi Alvaro,

Let me try and answer your questions...

alvaro wrote:
> Hi,
> i'm curious about XMS, it looks like it is required for building the
> SAM extension, is that right?

The current level of SAM uses XMS to connect to the various members of
the IBM messaging and queuing product family so yes it is required to
build the extension.

> What sort of license is XMS released under? It wasn't very clear on the
> XMS readme filed, it just said "Licensed Materials - Property of IBM"
> Is there anyway to bundle the XMS code inside of the SAM source?
> Registering with IBM and installing the XMS code was a bit of nuisance.

I agree it's not ideal that you have to register on the IBM site to
access the XMS package but currently we are sort of stuck with this.
XMS is freely available for download from IBM but as it is not itself
open source we can't bundle it with the SAM source on PECL.

In fact I think as a longterm strategy bundling the XMS component with
SAM would be the wrong thing to do. XMS gives us an easy way to get to
all the IBM messaging products but it doesn't provide a way of talking
to anything else. I have been putting some thought to how to allow SAM
to connect to other messaging technologies and there are a variety of
options. For some of these configurations we would not need XMS at all
and so having it in the package would actually be a nuisance rather
than a benefit. I can envisage a library or hierarchy of support
packages under or within SAM each supporting one or more wire
protocols. XMS support would be just one of these.

>
> I've emailed you before (alv...@epliant.com), i've been very busy, but
> i'm interested on adding support for the OpenWire protocol (native to
> ActiveMQ). I would also like to create RPMs for Red Hat boxes.
>
> Thanks,
> Alvaro

No problem. The world is full of busy people and I figured you would
respond when you had a free moment. :-) I would be interested in
discussing OpenWire etc. with you further. It's certainly a possible
for inclusion in a range of connection technologies and it would also
allow us to connect to WebSphere CE (the IBM open-source server). We
should probably continue this discussion over e-mail.

Cheers
Dave

[D.S.R...@googlemail.com]

Version 1.1.0 of SAM has recently been released and this removes the
hard and fast requirement for the IBM XMS package to be installed to
build or deploy. A generic extension mechanism has been added to SAM
to make it easy to add C or PHP protocol implementations and the XMS
support is now optional.

Cheers
Dave