>> Web Service vs MS Message Queue

[Jonathan]

Hi, I'm new to dot Net.

When would I use MS Message Queue rather than Web Service?

The situation is this... The data source is a remote application.
Periodically (perhaps once an hour) this application will send to our
application data in XML format.

At this stage it is envisaged that there is only one data source. However,
there is discussion that at a later date there may be more than one remote
data source.

Any ideas or recommendations appreciated :-)

Thanks
Jonathan

[Onawole, Clement Oladapo]

Your described scenerio is not very clear. I will be able to answer your
question better if you can rephrase it a bit.

Use message queues for remote sources that are on an un-reliable like i.e.
on a link that is not guaranteed to be available all the time e.g a GSM
mobile network for SMS where recipient subscriber may have switched off
their phone. Web services on the other is good for heterogenous remote
parties and as it is on a link that's bound to be available most of the
time.
"Jonathan" <Jo******@discussions.microsoft.com> wrote in message
news:51**********************************@microsof t.com...

Hi, I'm new to dot Net.

When would I use MS Message Queue rather than Web Service?

The situation is this... The data source is a remote application.
Periodically (perhaps once an hour) this application will send to our
application data in XML format.

At this stage it is envisaged that there is only one data source. However,
there is discussion that at a later date there may be more than one remote
data source.

Any ideas or recommendations appreciated :-)

Thanks
Jonathan

[Jonathan]

Hi Onawole, I think that your response actually answers my question.

thanks

Jonathan

"Onawole, Clement Oladapo" wrote:

Your described scenerio is not very clear. I will be able to answer your
question better if you can rephrase it a bit.

Use message queues for remote sources that are on an un-reliable like i.e.
on a link that is not guaranteed to be available all the time e.g a GSM
mobile network for SMS where recipient subscriber may have switched off
their phone. Web services on the other is good for heterogenous remote
parties and as it is on a link that's bound to be available most of the
time.
"Jonathan" <Jo******@discussions.microsoft.com> wrote in message
news:51**********************************@microsof t.com...

Hi, I'm new to dot Net.

When would I use MS Message Queue rather than Web Service?

The situation is this... The data source is a remote application.
Periodically (perhaps once an hour) this application will send to our
application data in XML format.

At this stage it is envisaged that there is only one data source. However,
there is discussion that at a later date there may be more than one remote
data source.

Any ideas or recommendations appreciated :-)

Thanks
Jonathan