Re: What multi-tier components to use

Hi,

> But I guess the statement "kbmMW is _fully_ service oriented" depends on
> what one means by "fully." My experience was that I had to write a series of
> IF/THEN statements to use some basic custom services (eg MyGetServerTime,
> MyAddNumbers, etc).

Thats part of the flexibility of kbmMW. You can add all the functionality you want in a service, and divide it to your
hearts content.
All in one service where you seperate on the function name, or multiple services containing less code in each.

The real misconception is that service oriented architecture implies strongly typed RPC calls.
The two things has nothing to do with eachother. You can easily have a strongly typed RPC call which isnt of much use in
a service oriented architecture, and you can have a service oriented architecture which isnt using strongly typed RPC
etc.

Lots of implementations are strongly typed (COM - can exist as both strongly typed and weakly, EJB etc), and they have
the advantages that when you code, you can in the IDE directly see what arguments you can use and of which types. But at
the same time they have the disadvantages of flexibility. One have to be very careful when updating serverside business
code, not to touch the IDL (the interface description) part... in other words for example not to change an argument from
being of type float to double, or add optional arguments etc. If one do so, the concept of strongly typed RPC calls
require you to redistribute a new client that match exactly with the server and visa versa.

kbmMW has been designed not to have that problem. A newer server can still serve older clients if needed.

If people want a strongly typed interface using kbmMW, they can easily have that by doing the exact same thing that is
happening in all the other strongly typed frameworks, namely make a class which contains properties, events and methods,
and let the method be the one making the call to the server. On the server you have a similar class which takes the call
and creates an instance of the class extracting the provided arguments into the properties etc.
Its basic mashalling and unmarshalling and really no magic at all.


--

best regards
Kim Madsen
kbm@xxxxxxxxxxxxxxxxxxxxxxxxx
www.components4developers.com

The best components for the best developers
kbmMW - kbmMemTable - kbmWABD - kbmX10


.