Advice on Web Service modelling

[Anders K. Olsen]

Hello group

I would like some advice on how to model my webservices.

Our application is made up of a number of independent modules that handle
different parts of the application logic. It is a client-server application,
where the server exposes some web services that the clients can use.

Each module is not completely independent but some of them share some common
logic. The common logic is concerns how to load TimeSeries objects.

There is a common method of loading TimeSeries, and that logic is
implemented in a common web-service. Some of the other modules add to this
common logic by specifying individual filtering options. These extra
filtering options are not share by the other modules.¨

I would like to have several web services:

1) CommonService - knows how to load a TimeSeries in the common way.
2) SpecializedServ ice1 - Adds specific filtering options to CommonService.
3) SpecializedServ ice2 - Adds specific filtering options to CommonService.

All services return the same kind of result: TimeSeries objects.

On my client, I would have a CommonService that all modules could use to
access the TimeSeries in the common way. I could then create specific
services on the client that knows how to use the specialized web services.

My application is implemented in C# (both client and server). I use Visual
Studio 2005 to generate my web references on the client.

I would then generate a web reference for CommonService and another web
reference for SpecializedServ ice1. I can do that without any problems.
However even though they both return the same kind of objects: TimeSeries,
the TimeSeries objects are not the same for the two web references. This is
because Visual Studio generates different objects for each web reference.

Is there a good way to solve the problem with different type of TimeSeries
objects?

Would it be a better solution to just make one web service:
TimeSeriesServi ce that knows how to loading TimeSeries in all possible ways?
This would mean that a client module that only need to load TimeSeries in
the Specialized1 way would also be able to load them in Specialized2 way.

Thank you for your advice.

Regards
Anders

[John Saunders]

"Anders K. Olsen" <ak*****@hotmai l.comwrote in message
news:e0******** ******@TK2MSFTN GP03.phx.gbl...

Hello group

I would like some advice on how to model my webservices.

Our application is made up of a number of independent modules that handle
different parts of the application logic. It is a client-server
application, where the server exposes some web services that the clients
can use.

Each module is not completely independent but some of them share some
common logic. The common logic is concerns how to load TimeSeries objects.

There is a common method of loading TimeSeries, and that logic is
implemented in a common web-service. Some of the other modules add to this
common logic by specifying individual filtering options. These extra
filtering options are not share by the other modules.¨

I would like to have several web services:

1) CommonService - knows how to load a TimeSeries in the common way.
2) SpecializedServ ice1 - Adds specific filtering options to CommonService.
3) SpecializedServ ice2 - Adds specific filtering options to CommonService.

All services return the same kind of result: TimeSeries objects.

On my client, I would have a CommonService that all modules could use to
access the TimeSeries in the common way. I could then create specific
services on the client that knows how to use the specialized web services.

My application is implemented in C# (both client and server). I use Visual
Studio 2005 to generate my web references on the client.

I would then generate a web reference for CommonService and another web
reference for SpecializedServ ice1. I can do that without any problems.
However even though they both return the same kind of objects: TimeSeries,
the TimeSeries objects are not the same for the two web references. This
is because Visual Studio generates different objects for each web
reference.

Is there a good way to solve the problem with different type of TimeSeries
objects?

Would it be a better solution to just make one web service:
TimeSeriesServi ce that knows how to loading TimeSeries in all possible
ways? This would mean that a client module that only need to load
TimeSeries in the Specialized1 way would also be able to load them in
Specialized2 way.

I'd just use one web service with multiple operations, each for the
different way to load a TimeSeries.

John

[Anders K. Olsen]

"John Saunders" <john.saunder s at trizetto.comwro te in message
news:uP******** ******@TK2MSFTN GP03.phx.gbl...

"Anders K. Olsen" <ak*****@hotmai l.comwrote in message
news:e0******** ******@TK2MSFTN GP03.phx.gbl...
Would it be a better solution to just make one web service:

>TimeSeriesServ ice that knows how to loading TimeSeries in all possible
ways? This would mean that a client module that only need to load
TimeSeries in the Specialized1 way would also be able to load them in
Specialized2 way.

I'd just use one web service with multiple operations, each for the
different way to load a TimeSeries.

Hello John

Thanks for your advice. I think your are right, that is probably the best
way to do it.

Regards
Anders