Portable object (computing): Difference between revisions

Content deleted Content added

Inline

Latest revision as of 18:22, 14 November 2024

In distributed programming, a portable object is an object which can be accessed through a normal method call while possibly residing in memory on another computer.^[1] It is portable in the sense that it moves from machine to machine, irrespective of operating system or computer architecture. This mobility is the end goal of many remote procedure call systems.

An advantage of portable objects is that they are easy to use and expressive, allowing programmers to be completely unaware that objects reside in other locations. Detractors cite this as a fault, as some programmers will not expect network-related errors or the unbounded nondeterminism associated with large networks.

References

^ WO2006136923A1, Castillo, Laurent & Siegelin, Christoph, "Method and system using a portable object for providing an extension to a server", issued 2006-12-28

This computer science article is a stub. You can help Wikipedia by expanding it.

[1] WO2006136923A1, Castillo, Laurent & Siegelin, Christoph, "Method and system using a portable object for providing an extension to a server", issued 2006-12-28

[1]

@@ Line 1: / Line 1: @@
 {{Short description|Object in distributed programming}}
 {{redirect|.po|the extension as used with GNU|GNU gettext|the internationalized top-level domain|.рф}}
+<!-- Please do not remove or change this AfD message until the discussion has been closed. -->
-{{Unreferenced|date=January 2009}}
+{{Article for deletion/dated|page=Portable object (computing)|timestamp=20241114132843|year=2024|month=November|day=14|substed=yes|help=off}}
-In [[distributed programming]], a '''portable object''' is an [[object (computer science)|object]] which can be accessed through a normal [[method (computer science)|method]] call while possibly residing in memory on another [[computer]].  It is portable in the sense that it moves from machine to machine, irrespective of [[operating system]] or [[computer architecture]].  This mobility is the end goal of many [[remote procedure call]] systems.
+<!-- Once discussion is closed, please place on talk page: {{Old AfD multi|page=Portable object (computing)|date=14 November 2024|result='''keep'''}} -->
+<!-- End of AfD message, feel free to edit beyond this point -->
+In [[distributed programming]], a '''portable object''' is an [[object (computer science)|object]] which can be accessed through a normal [[method (computer science)|method]] call while possibly residing in memory on another [[computer]].<ref>{{Cite patent|number=WO2006136923A1|title=Method and system using a portable object for providing an extension to a server|gdate=2006-12-28|invent1=Castillo|invent2=Siegelin|inventor1-first=Laurent|inventor2-first=Christoph|url=https://patents.google.com/patent/WO2006136923A1/}}</ref>  It is portable in the sense that it moves from machine to machine, irrespective of [[operating system]] or [[computer architecture]].  This mobility is the end goal of many [[remote procedure call]] systems.
-The advantage of portable objects is that they are easy to use and very [[expressive power (computer science)|expressive]], allowing [[programmer]]s to be completely unaware that objects reside in other locations.  Detractors cite this as a fault, as naïve programmers will not expect [[computer network|network-related]] errors or the [[unbounded nondeterminism]] associated with large networks.
+An advantage of portable objects is that they are easy to use and [[expressive power (computer science)|expressive]], allowing [[programmer]]s to be completely unaware that objects reside in other locations.  Detractors cite this as a fault, as some programmers will not expect [[computer network|network-related]] errors or the [[unbounded nondeterminism]] associated with large networks.
 ==See also==