Talk:Middleware (distributed applications): Difference between revisions

Content deleted Content added
Samehz (talk | contribs)
EKhayaICT (talk | contribs)
Line 101:
Thanks
[[User:Samehz|SZ]] 06:59, 1 December 2007 (UTC)
 
== Client/Server? ==
 
"This technology evolved to provide for interoperability in support of the move to client/server architecture." After this somewhat puzzling statement in the third sentence of this article, I couldn't help looking around to see what basis there was for the statement. In the classification of middleware, the word client appears again, so I presume client/server refers to RPC, which sure looks like client/server. And it is! But it's not a "client/server architecture", that's something completely different. A client/server architecture is a centralised architecture, which bundles resources in a server (which can of course be distributed) and maintains only end-user processing in the client (who consumes the resources). RPC is a distributed method of computing, and so it could be extensively used only withint the server portion of the client/server architecture as is often the case.
 
Am changing the sentence --> "distributed architecture"
 
[[User:EKhayaICT|EKhayaICT]] ([[User talk:EKhayaICT|talk]]) 06:52, 18 April 2008 (UTC)