sc> "Rodrigo García" wrote:
sc>
>> Hi.
>>
>> The use of Serviced Components makes sense when you need distributed
>> transactions (two-phase transactions).
>> e.g. you need to read some values from a database, enqueue a message
>> with
>> msmq, and update another database in an all-or-nothing fashion. You
>> could do
>> those things manually but it gets complicated. The solution is to put
>> that in
>> a Serviced Component and let the DTC carry out the transactions
>> I hope it helps.
>>
>> "serge calderara" wrote:
>>
>>> Dear all,
>>>
>>> I am trying to catch the real used of a serviced componenent
>>> I get an example where a libarary named Account has been defined as
>>> a
>>> serviced component by inheriting from System.ServiceComponent class
>>> This library is performing some action on an SQL dtabase tables
>>> Then I have a client application named Transaction with create an
>>> Instance of the Account class on the form load event, then update
>>> object interface with received data from the database through the
>>> account component.
>>>
>>> So far so good, but then why making those thig so complicated, I
>>> could do the same this with a normal Account assembly ?
>>>
>>> Does any one could explain me what is the idea behind this example
>>> then
>>>
>>> thnaks for your help
>>> regards
>>> serge

"Michael Nemtsev" wrote:

> Hello serge,
>
> WebServices doing only part of that things. You should unterstand that WS
> gives u a platform-independent abstraction layer.
> It's not a substitute for ES.
>
> WS can't manipulate transactions as ES, WS is slower then ES and etc.
> I recomend to read about ES to understand its power
>
> sc> web services are doing the same thing...
> sc>
> sc> do you have any simple samples ?
> sc> By the way is it something whcih is really used today? i dont think
> sc> so, web
> sc> service goes on the scene
> sc> serge
> sc>
> >>
> >> Nope, Services component is used in distributed application - to
> >> create scalable architecture, where are parts of system are
> >> physically distributed.
> >>
> >> It's not necessary to handle transaction with DB, u can handle any
> >> resource with transactions, even files
> >>
> >> sc> So does it mean that all this serviced component is use and only
> >> use
> >> sc> to handle database transaction ?
> >> sc>
> >> sc> "Rodrigo García" wrote:
> >> sc>
> >>>> Hi.
> >>>>
> >>>> The use of Serviced Components makes sense when you need
> >>>> distributed
> >>>> transactions (two-phase transactions).
> >>>> e.g. you need to read some values from a database, enqueue a
> >>>> message
> >>>> with
> >>>> msmq, and update another database in an all-or-nothing fashion. You
> >>>> could do
> >>>> those things manually but it gets complicated. The solution is to
> >>>> put
> >>>> that in
> >>>> a Serviced Component and let the DTC carry out the transactions
> >>>> I hope it helps.
> >>>> "serge calderara" wrote:
> >>>>
> >>>>> Dear all,
> >>>>>
> >>>>> I am trying to catch the real used of a serviced componenent
> >>>>> I get an example where a libarary named Account has been defined
> >>>>> as
> >>>>> a
> >>>>> serviced component by inheriting from System.ServiceComponent
> >>>>> class
> >>>>> This library is performing some action on an SQL dtabase tables
> >>>>> Then I have a client application named Transaction with create an
> >>>>> Instance of the Account class on the form load event, then update
> >>>>> object interface with received data from the database through the
> >>>>> account component.
> >>>>> So far so good, but then why making those thig so complicated, I
> >>>>> could do the same this with a normal Account assembly ?
> >>>>>
> >>>>> Does any one could explain me what is the idea behind this example
> >>>>> then
> >>>>>
> >>>>> thnaks for your help
> >>>>> regards
> >>>>> serge
>
> ---
> WBR,
> Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour
>
> "At times one remains faithful to a cause only because its opponents do not
> cease to be insipid." (c) Friedrich Nietzsche
>
>