What do you mean by a polymorphic service? One that can handle
multiple message types, or one that is polymorphic in terms of the
contract it offers to consumers.
If its the former then I don't see why not, if the service is
something like "DataCleansing" and you can pass in multiple different
data types for cleansing and it returns the cleansed data.
If its the later then I think it might get a little tricky if the
service changes its behaviour based on what it is passed!
On 09/09/06, jeffrschneider <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
>
> Are polymorphic services a good idea?
>
> If they are implemented in a message oriented manner, should you:
> - Use the header or the body to indicate the polymorphic context
>
> - If it is in the body, should it be implicit (based on type) or
> explicit based on content?
>
> :-)
> Jeff
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
