Re: Confusion: Server side creation of CAO's
From: Roy Chastain (roy_at_kmsys.com)
Date: 04/16/04
- Next message: Sunny: "Re: Real Basic Stuff"
- Previous message: David Waldock: "Re: Real Basic Stuff"
- In reply to: Sunny: "Re: Confusion: Server side creation of CAO's"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 16 Apr 2004 13:14:43 -0400
Thank you.
Your 2 c are probably worth more than 2 :-)
Need to think about this one some.
On Fri, 16 Apr 2004 11:31:39 -0500, Sunny <sunnyask@icebergwireless.com> wrote:
>Hi Roy,
>
>> Sunny, would you please expand on your statement about the interface/abstract class being
>> "more flexible and more scalable". More flexible, I see, but more scalable. How so?
>Lets say, you decide to add additional functionality to your server
>object. The you put that additional functions in a new interface. You
>make your server object implement both interfaces. The, the old clients
>still can use the server the way they used to, and new clients can use
>the new interface for increased functionality. You do not have to
>change/recompile the old clients, they'll continue to work whatever you
>do with the server. Isn't is scalable?
>
>>
>> If someone could give me a reason instead of theories and innuendo about SoapSuds vs. interface etc, I would be very willing to go
>> that way.
>>
>
>With soapsuds you are static. You prepare the remoted class, you
>soapsuds, and you integrate it with the client. Every change at server
>side will make the client to brake. Using base abstract classes or
>interfaces helps you to change/bug fix the server object without the
>need of rebuilding and redeploying the client.
>
>Just my 2 c.
>
>Sunny
-------------------------------------------
Roy Chastain
KMSystems, Inc.
- Next message: Sunny: "Re: Real Basic Stuff"
- Previous message: David Waldock: "Re: Real Basic Stuff"
- In reply to: Sunny: "Re: Confusion: Server side creation of CAO's"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|