The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jan. 23, 2007
Filed:
Jan. 22, 2002
Bernard A. Traversat, San Francisco, CA (US);
Mohamed M. Abdelaziz, Santa Clara, CA (US);
Michael J. Duigou, Fremont, CA (US);
Eric Pouyoul, San Francisco, CA (US);
Jean-christophe Hugly, Palo Alto, CA (US);
LI Gong, Los Altos, CA (US);
William J. Yeager, Menlo Park, CA (US);
William N. Joy, Aspen, CO (US);
Michael J. Clary, Monte Sereno, CA (US);
Bernard A. Traversat, San Francisco, CA (US);
Mohamed M. Abdelaziz, Santa Clara, CA (US);
Michael J. Duigou, Fremont, CA (US);
Eric Pouyoul, San Francisco, CA (US);
Jean-Christophe Hugly, Palo Alto, CA (US);
Li Gong, Los Altos, CA (US);
William J. Yeager, Menlo Park, CA (US);
William N. Joy, Aspen, CO (US);
Michael J. Clary, Monte Sereno, CA (US);
Sun Microsystems, Inc., Santa Clara, CA (US);
Abstract
A system and method for establishing communications channels between and among peers in a peer-to-peer networking environment. Pipes may be used as communication channels for sending and receiving messages and other data between services or applications over input and output endpoints. Pipes may be asynchronous, unidirectional, stateless and unreliable. Bidirectional pipes may also be supported. Pipes may have ends that may be moved around and bound to different peers at different times. Point-to-point and propagate pipes may be supported. Pipes may connect peers that have a direct physical link and peers that do not have a direct link. Peers may communicate through pipes without knowing on which peer a pipe endpoint is bound. A message is sent to all peer endpoints currently connected (listening) to the pipe. The set of connected endpoints may be obtained from a pipe service using a pipe binding protocol.