Is it possible (or common practice) to have the business facade layer of the
web services layer implemented as .net remoting component(s).
While the web services provide the necssary access to external web/Java
clients, the .net remoting is used to comminicate between internal (company
wide, .net, same network) applications who can benefit from the .net remoting
performance benefits over web services. The web services layer will actually
invoke the remoting components internally to fulfill the functionality.
I would like to know what is the common design practice in this distributed
scenario.
--
Kind regards,
SB