Methods and apparatus to improve interprocess communication

Abstract

Methods, apparatus, systems and articles of manufacture are disclosed to improve interprocess communication. An example apparatus to improve network transmission efficiency of a sending peer includes an encoder interface to prevent an encoder from encoding data in a native format to a target format associated with a requesting peer in response to a transmission trigger, a composite interface description (CID) engine to generate architecture agnostic metadata of the data in the native format, a composite layout description (CLD) engine to generate architecture specific metadata of the data in the native format, the architecture specific metadata identifying offset values associated with elements of the data in the native format, and a client payload engine to improve the network transmission efficiency by sending unencoded data combined with the architecture agnostic metadata and the architecture specific metadata to the requesting peer having an architecture different than that of the sending peer.

1 .- 25 . (canceled) 
     
     
         26 . An apparatus to resolve data retrieved by a receiving peer having an incompatible architectural format, comprising:
 a server storage interface to retrieve:
 a composite having the incompatible architectural format; 
 a client-side composite interface description (CID) having architecture agnostic metadata associated with the composite; and 
 a client-side composite layout description (CLD) having architecture specific metadata associated with the composite; 
   a server metadata manager to:
 encode a server-side CID with the architecture agnostic metadata of the client-side CID; 
 encode a server-side CLD with the architecture specific metadata of the client-side CLD; and 
   a translation engine to generate offset values for respective elements of the server-side CLD based on an architecture type of the receiving peer.   
     
     
         27 . An apparatus as defined in  claim 26 , further including a request manager to detect a first request to render the data having the incompatible architectural format. 
     
     
         28 . An apparatus as defined in  claim 27 , further including a format resolver to identify a format type of the first request. 
     
     
         29 . An apparatus as defined in  claim 28 , wherein the translation engine is to translate the respective elements of the data retrieved by the receiving peer based on (a) offset values of the respective elements and (b) the format type of the first request. 
     
     
         30 . An apparatus as defined in  claim 29 , wherein the translation engine is to forward the translated respective elements of the data to a requestor of the first request. 
     
     
         31 . An apparatus as defined in  claim 27 , wherein the server storage interface is to reduce a computational demand of the receiving peer during a second request by associating the client-side CID and the client-side CLD with a receiving peer metadata reference. 
     
     
         32 . An apparatus as defined in  claim 26 , wherein the server storage interface is to associate the server-side CID and the server-side CLD with a receiving peer metadata reference. 
     
     
         33 . An apparatus as defined in  claim 32 , wherein the server metadata manager is to improve a computational efficiency of the receiving peer by bypassing encoding of the server-side CID and the server-side CLD when the data retrieved by the receiving peer includes a sending peer metadata reference that matches the receiving peer metadata reference. 
     
     
         34 . An apparatus as defined in  claim 33 , wherein the server metadata manager is to retrieve the server-side CID and the server-side CLD from a local storage when the sending peer metadata reference matches the receiving peer metadata reference. 
     
     
         35 . A method to resolve data retrieved by a receiving peer having an incompatible architectural format, comprising:
 retrieving a composite having the incompatible architectural format, a client-side composite interface description (CID) having architecture agnostic metadata associated with the composite, and a client-side composite layout description (CLD) having architecture specific metadata associated with the composite;   encoding a server-side CLD with the architecture agnostic metadata of the client-side CID, and encoding a server side CLD with the architecture specific metadata of the client-side CLD; and   generating offset values for respective elements of the server-side CLD based on an architecture type of the receiving peer.   
     
     
         36 . A method as defined in  claim 35 , further including detecting a first request to render the data having the incompatible architectural format. 
     
     
         37 . A method as defined in  claim 36 , further including identifying a format type of the first request. 
     
     
         38 . A method as defined in  claim 37 , further including translating the respective elements of the data retrieved by the receiving peer based on (a) offset values of the respective elements and (b) the format type of the first request. 
     
     
         39 . A method as defined in  claim 38 , further including forwarding the translated respective elements of the data to a requestor of the first request. 
     
     
         40 . A method as defined in  claim 36 , further including reducing a computational demand of the receiving peer during a second request by associating the client-side CID and the client-side CLD with a receiving peer metadata reference. 
     
     
         41 . A method as defined in  claim 35 , further including associating a server-side CID and the server-side CLD with a receiving peer metadata reference. 
     
     
         42 . A method as defined in  claim 41 , further including improving a computational efficiency of the receiving peer by bypassing encoding of the server-side CID and the server-side CLD when the data retrieved by the receiving peer includes a sending peer metadata reference that matches the receiving peer metadata reference. 
     
     
         43 . A method as defined in  claim 42 , further including retrieving the server-side CID and the server-side CLD from a local storage when the sending peer metadata reference matches the receiving peer metadata reference. 
     
     
         44 . A tangible computer readable storage medium comprising computer readable instructions which, when executed, cause a processor to at least:
 retrieve a composite having an incompatible architectural format, a client-side composite interface description (CID) having architecture agnostic metadata associated with the composite, and a client-side composite layout description (CLD) having architecture specific metadata associated with the composite;   encode a server-side CLD with the architecture agnostic metadata of the client-side CID, and encode a server side CLD with the architecture specific metadata of the client-side CLD; and   generate offset values for respective elements of the server-side CLD based on an architecture type of a receiving peer.   
     
     
         45 . A tangible computer readable storage medium as defined in  claim 44 , wherein the computer readable instructions are to cause the processor to detect a first request to render data having the incompatible architectural format. 
     
     
         46 . A tangible computer readable storage medium as defined in  claim 45 , wherein the computer readable instructions are to cause the processor to identify a format type of the first request. 
     
     
         47 . A tangible computer readable storage medium as defined in  claim 46 , wherein the computer readable instructions are to cause the processor to translate the respective elements of the data retrieved by the receiving peer based on (a) offset values of the respective elements and (b) the format type of the first request. 
     
     
         48 . A tangible computer readable storage medium as defined in  claim 47 , wherein the computer readable instructions are to cause the processor to forward the translated respective elements of the data to a requestor of the first request. 
     
     
         49 . A tangible computer readable storage medium as defined in  claim 45 , wherein the computer readable instructions are to cause the processor to reduce a computational demand of the receiving peer during a second request by associating the client-side CID and the client-side CLD with a receiving peer metadata reference. 
     
     
         50 . A tangible computer readable storage medium as defined in  claim 44 , wherein the computer readable instructions are to cause the processor to associate a server-side CID and the server-side CLD with a receiving peer metadata reference.