Server-Side Components: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
A '''server-side component model''' is an architecture for developing distributed business objects. It combines the |
A '''server-side component model''' is an architecture for developing distributed business objects. It combines the |
||
accessibility of [[Distributed Systems|distributed systems]] with the flexibility of [[Business Objects|business objects]]. |
accessibility of [[Distributed Systems|distributed systems]] with the flexibility of [[Business Objects|business objects]]. |
||
Server-side components are used on the middle-tier of an [[application-server]]. The [[:Introduction|Enterprise JavaBeans]] and |
'''Server-side components''' are used on the middle-tier of an [[application-server]]. The [[:Introduction|Enterprise JavaBeans]] and |
||
Microsoft's [[Microsoft .NET|.NET Framework]], for example, are standard server-side components. |
Microsoft's [[Microsoft .NET|.NET Framework]], for example, are standard server-side components. |
||
See also |
|||
---- |
|||
* [[Component Transaction Monitors]] |
|||
Revision as of 15:25, 11 November 2004
A server-side component model is an architecture for developing distributed business objects. It combines the accessibility of distributed systems with the flexibility of business objects. Server-side components are used on the middle-tier of an application-server. The Enterprise JavaBeans and Microsoft's .NET Framework, for example, are standard server-side components.
See also