Re: Need advise on concept ???

To read or write to a queue on a different machine will require valid credentials for the other machine. I strongly suggest creating a domain account for this purpose and assign the account the appropriate permissions for the queues that you will be using.

--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com



"calderara" <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:35460F17-C5D3-4C2B-8528-4ADB49AFEB38@xxxxxxxxxxxxx:

Hi bryan...

I have some more clarification based on those messages.
If I ma using a WIndows service as a "message dispatcher", that service will
simply place the proper message inside the proper queue to which my library
will be register to. But my service will runing as a local Servcice account,
so in a separate process as my library which could be as well as local or
distributed on a differetn PC.
In the case it is distributed, how my library can register to a Queue which
is created on an other PC by this Service I ma planning to build ?

thnaks for help
regards
serge

"Bryan Phillips" wrote:

> Web services are a little slower than MSMQ but they are easier to
> integrate cross-platform. If you are only using Windows, MSMQ is fine.
>
> The Message Dispatcher is a good approach.
>
> By loosely coupled, they mean don't use direct references that cross the
> boundaries of application tiers. Using messages or interfaces would
> satisfy this requirement.
>
> Yes, your scenario would qualify as being loosely coupled. If this is a
> Windows Forms app, you will want to look at using the Composite UI
> Application Block to help with the UI side on your message handling
> architecture.
>
> --
> Bryan Phillips
> MCSD, MCDBA, MCSE
> Blog: http://bphillips76.spaces.live.com
>
>
>
> "calderara" <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C43B867E-A59C-4FCA-B793-5DC42CEC0367@xxxxxxxxxxxxx:
>
> > Thanks for your reply...
> > Web service might be slower than MSMQ ?
> > Does the "Message Dispatcher" define as a service is a good approach for
> > that situation?
> >
> >
> > I have been been reading when defining components architecture for an
> > application that components should be loosly couple whenever it is possible.
> > Based on that does it mean that User interface which need to communicate
> > with a buisness logic needs to do that through messages instead of having a
> > reference to it ?
> >
> > For instance I have a user interface with a button which need to get
> > information from a logic contains in myLIb.dll.
> > In normal way I woul do it by having a reference to that lib and then call a
> > function inside myLib object to perform the proper action.
> >
> > In loosly coupls way, do it means that the button_click should send a
> > message somehow that the library will monitor and answer ?
> >
> > serge
> >
> > "Bryan Phillips" wrote:
> >
> > > MSMQ would work, but you could also use web services since they also
> > > support asynchronous calls.
> > >
> > > --
> > > Bryan Phillips
> > > MCSD, MCDBA, MCSE
> > > Blog: http://bphillips76.spaces.live.com
> > >
> > >
> > >
> > > "calderara" <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:C4B0A39B-1FB3-4981-9380-A2070131972E@xxxxxxxxxxxxx:
> > >
> > > > Dear all,
> > > >
> > > > I have different .NET libraries which should answer and execute proper
> > > > operation based on external application message. Each assembly should listen
> > > > from its own messages.
> > > >
> > > > Messages are coming from an external application and my own assenblies
> > > > should answer to those incomimg messages.
> > > >
> > > > For that I was thinking to build a service that I could named "Message
> > > > dispatcher". That service will listen to incoming message and then send it to
> > > > proper assembly for processing.
> > > >
> > > > Note that message will be asynchrone and as a first step all assemblies will
> > > > be on the same machine.
> > > >
> > > > For message handling I was thinking first to use this Message queue from
> > > > COM+ component but I have no experience at all on those messaging process.
> > > >
> > > > My questions are:
> > > >
> > > > 1 - Does the message dispatcher as a service is a good approach ?
> > > > 2 - Does MS Queue under COM + is a good approach ? is it har to set up
> > > >
> > > > Thnaks for all
> > > > regards
> > > > serge
> > >
> > >
>
>

.

Loading