Author |
Message
|
GenCode |
Posted: Wed Jan 04, 2017 11:30 am Post subject: XMS or amqmnet |
|
|
Novice
Joined: 10 Sep 2015 Posts: 21
|
When starting a new project should I be using XMS or amqmnet or does it really matter?
I am asking because I though I read that amqmnet was on a EOL path but not sure where I read that. Is that true?
Thanks, Ed,
Last edited by GenCode on Wed Jan 04, 2017 11:44 am; edited 1 time in total |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jan 04, 2017 11:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
GenCode |
Posted: Wed Jan 04, 2017 11:42 am Post subject: |
|
|
Novice
Joined: 10 Sep 2015 Posts: 21
|
Yes I know they are 2 different things and I have projects that use both.
That was not the question, the question was is one End Of Life.
From the reply I assume that neither is at end of life so use whatever works best for what I am doing. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jan 04, 2017 12:26 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I don't see any notes about deprecation (which would eventually lead to out of support) for XMS.
I do see
Code: |
IBM MQ transport SOAP .NET 1 and 2
The IBM MQ transport SOAP .NET 1 and 2 client is deprecated. The functionality that is provided by this client is considered back-level. Use the IBM MQ custom channel for Microsoft Windows Communication Foundation (WCF) as an alternative. |
So maybe that's what (both of us) were thinking of. Very vague memories for me. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
GenCode |
Posted: Wed Jan 04, 2017 12:46 pm Post subject: |
|
|
Novice
Joined: 10 Sep 2015 Posts: 21
|
I guess if there is no real reason to migrate to XMS
Thanks for the reply.
Very interesting that we have 2 .NET API paths that seem to accomplish the same thing (basically). |
|
Back to top |
|
 |
|