Editing Method stub (section)

==Related==

===Distributed computing===

In [[distributed computing]], ''stub'' is like a [[mock object]] {{endash}} [[simulation|simulate]]s existing code, such as a [[Subroutine|procedure]] on a remote machine. Such stubs can be useful in [[porting]].

In [[Remote Method Invocation|RMI]] nomenclature, a stub on the client-side communicates with a [[Skeleton (computer science)|skeleton]] on the server-side.<ref>{{cite book
 | last1         = Freeman
 | first1        = Eric
 | authorlink1   = 
 | last2         = Freeman
 | first2        = Elisabeth 
 | authorlink2   = 
 | last3         = Kathy
 | first3        = Sierra
 | authorlink3   = 
 | last4         = Bert
 | first4        = Bates
 | authorlink4   = 
 | editor1-last   = Hendrickson
 | editor1-first  = Mike
 | editor2-last  = Loukides
 | editor2-first = Mike
 | year          = 2004
 | title         = Head First Design Patterns
 | volume        = 1
 | page          = 440
 | publisher     = O'REILLY
 | format        = paperback
 | isbn          = 978-0-596-00712-6
 | accessdate    = 2012-08-28
 | url           = http://shop.oreilly.com/product/9780596007126.do
}}</ref>

===Windows/DOS===

In [[Windows]] and [[DOS]], ''stub'' is like a [[Shim (computing)|shim]] {{endash}} small interface code left in [[conventional memory]] by [[self-relocation|self-relocating]] resident drivers which move most of themselves into [[upper memory]], the [[high memory area]], [[expanded memory|expanded]] or [[extended memory]] as well as similar stubs to allow the relocated code to communicate with [[real-mode]] DOS in conjunction with [[DOS extender]]s (like [[DOS Protected Mode Interface|DPMI]], [[DOS Protected Mode Services|DPMS]], [[CLOAKING (DOS extender)|CLOAKING]] or [[NetWare I/O Subsystem|NIOS]]).