How to mix interfaces and web services...
Imagine you need to implement a WS API to manage a variety of objects.
Each object shares a common protocol, like Fetch, Store, Validate, Publish...
but also may need to add object-specific methods.
So the problem is, what is an approach to enabling a client to deal with
a common interface to different objects in a generic way?
It seems that at least for ASP.NET, there's no help in identifying different
web service providers as adhering to a common contract (interface).
So perhaps the way to solve this is on the server, to implement the "interface"
and the "object identity" is a first parameter, which re-invokes the method
on a real interface of a real object.
Any additional thoughts or ideas are appreciated!
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL