a vague sense of disorientation when I read from someone so obviously
knowledgeable the statement, "I'm not sure what MQSeries is". I bet
you IBM account manager would have been even more worried!
Enjoy what remains of your weekend.
Gervas
PS I think you deserve an invitation to Hursley!
--- In [email protected], Stuart
Charlton <[EMAIL PROTECTED]> wrote:
>
> Gervas,
>
> My statement wasn't clear -- I'm quite aware of WebSphere MQ as a
product, having used it for years -- I mean I'm not sure whether it
is most appropriately used as a transfer or transport protocol (I've
treated it as both, in retrospect, depending on the context).
>
> Stu
>
> ----- Original Message ----
> From: Gervas Douglas <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Saturday, May 13, 2006 4:10:50 AM
> Subject: [service-orientated-architecture] Re: MQSeries vs. ESB
>
> Stuart,
>
> MQSeries is an IBM product. MQ stands for "message-queueing". I
> believe it was developed at Hursley, near Winchester in England -
a
> site some of you are well familiar with. As Anne has pointed out
> they now preface MQSeries with the sub-brand WebSphere. I am sure
IBM
> 's website can fill you in on the details.
>
> Gervas
>
> --- In [email protected], Stuart
> Charlton <stuartcharlton@> wrote:
> >
> > Fair enough, I can accept that distinction and note the
distinction
> in the future. I'm not sure what MQSeries is, I think it can be
> either transport or transfer, depending on whether the message
embeds
> operations or not.
> >
> > But I must admit, I've searched around a fair amount when you
first
> brought up the distinction, and have never heard a clear
distinction
> between transfer and transport other than in the terminological
notes
> of IETF RFC's and your own blog entries advocating the
distinction!
> I just don't think the terminological differences (while
reasonable
> and useful) are broadly established in the IT industry, though
> perhaps I'm wrong. The terms have in practice been used
> interchangeably, in my experience.
> >
> > Stu
> >
> >
> > ----- Original Message ----
> > From: Mark Baker <distobj@>
> > To: [email protected]
> > Sent: Tuesday, May 9, 2006 11:21:37 AM
> > Subject: Re: [service-orientated-architecture] Re: MQSeries vs.
ESB
> >
> > On 5/8/06, Stuart Charlton <stuartcharlton@> wrote:
> > > Let me correct myself and say "transfer" protocol instead of
> transport. Utimately, they're a way of moving bits with various
> differences in reliability, performance, available message
exchange
> patterns, schemes to describe resources.
> >
> > That's not the case, Stu. Transport protocols move bits,
transfer
> > protocols don't. Transfer protocols are used atop transport
> protocols
> > for this reason.
> >
> > Try looking at it this way; a trans*fer* protocol is to a trans*
> port*
> > protocol, as a supplier agreement is to a delivery truck. That
is,
> > transport only gets the goods to the door, while the
> > agreement/contract gets them *in* the door.
> >
> > Mark.
> >
> >
> >
> >
> >
> > SPONSORED LINKS
> > Computer
> software Computer aided
design
> software Computer
> job
>
> Soa Service-oriented
> architecture
> > YAHOO! GROUPS LINKS
> >
> > Visit your group "service-orientated-architecture" on the
web.
> > To unsubscribe from this group, send an email to:
> > [EMAIL PROTECTED]
> > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service.
> >
>
>
>
>
>
>
>
>
>
>
>
>
> SPONSORED LINKS
> Computer
software Computer aided design
software Computer
job
Soa Service-oriented
architecture
> YAHOO! GROUPS LINKS
>
> Visit your group "service-orientated-architecture" on the web.
> To unsubscribe from this group, send an email to:
> [EMAIL PROTECTED]
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
