Message Transport: A Message Transport is responsible for sending and/or receiving JXTA messages via an external network. A Message Transport may use whatever wire protocol it wishes in order to transmit messages between peers. Message Transports must pass the messages between peers unaltered.

Module: An abstraction used to represent any piece of "code" used to implement a behavior in the JXTA world. Network services are the mode common example of behavior that can be instantiated on a peer.

<<O>> Difference Topic JxtaGlossary (4 - 03 Nov 2005 - Main.bondolo)

    META TOPICPARENT    name="WebHome"
-   META TOPICPARENT
+ name="WebHome"
-<
<
+ JXTA Glossary
->
>
+ JXTA Glossary
-<
<
+ Advertisement
 JXTA's language-neutral metadata structures that describe peer
->
>
+ Advertisement
 JXTA's language-neutral metadata structures that describe peer
 		resources such as peers, peer groups, pipes, and services. Advertisements
		are represented as XML documents.
-<
<
+ Binding
 An implementation of the Project JXTA protocols for a particular
->
>
+ Binding
 An implementation of the Project JXTA protocols for a particular
 		environment (e.g., the J2SE^? platform binding).
 

 Codat
 The combination of a content (commonly a document or file) and a
-<
<
+		JXTA ID.
->
>
+	JXTA ID.
  Credential
 A token used to uniquely identify the sender of a message; can be 		used to provide message authorization.
-<
<
+ JXTA
 JXTA is not an acronym, and in particular the 		"J"does not refer to Java. JXTA is a made up word coined		by the project's original sponsor, Bill Joy. JXTA is derived from the
->
>
+ JXTA
 JXTA is not an acronym, and in particular the 		"J"does not refer to Java. JXTA is a made up word coined		by the project's original sponsor, Bill Joy. JXTA is derived from the
 		word Juxtapose, as in side by side. It is a recognition that
		peer-to-peer is juxtaposed to client server or Web based computing --
		what is considered today's traditional computing model.
-<
<
+ JXTA Core Specification
 The JXTA Core Specification consists of the required components		and behaviours which are present in all conforming JXTA
->
>
+ JXTA Core Specification
 The JXTA Core Specification consists of the required components		and behaviours which are present in all conforming JXTA
 		implementations. This includes the Peer Endpoint Protocol 
		(PEP) and the Peer Resolver Protocol (PRP).
-<
<
+ JXTA ID Format
 A JXTA ID Format is a scheme for representing it IDs of JXTA
->
>
+ JXTA ID Format
 A JXTA ID Format is a scheme for representing it IDs of JXTA
 		entities. Each ID Format is identified by as sub-namespace of the URN
		namespace "jxta".
-<
<
+ JXTA ID Type
 A JXTA ID Type is describes the characteristics of JXTA IDs which		refer to a particular sort of JXTA entity. Currently this includes peer
->
>
+ JXTA ID Type
 A JXTA ID Type is describes the characteristics of JXTA IDs which		refer to a particular sort of JXTA entity. Currently this includes peer
 		groups, peers, codats, pipes, module classes, module specifications and
		module impelmentations, but may be extended to refer to other types of
		entities in the future or in specific implementations.
-<
<
+ JXTA Standard Services
 The JXTA Standard Services are optional JXTA components and
->
>
+ JXTA Standard Services
 The JXTA Standard Services are optional JXTA components and
 		behaviours. Implementations are not required to provide these services,
		but are strongly recommended to do so.
		This includes Peer Discovery Protocol (PDP), Peer Information Protocol (PIP),
		Pipe Binding Protocol (PBP) and Rendezvous Protocol (RVP).
 

 Module
 An abstraction used to represent any piece of "code" used to
-<
<
+		implement a behavior in the JXTA world. Network services are the mode
->
>
+		implement a behavior in the JXTA world. Network services are the mode
 		common example of behavior that can be instantiated on a peer.
 

 Module Class
 Represents an expected behavior and an expected binding to support
 		specification is primarily used to access a module.
 

 Network Peer Group
 The base peer group for applications and services within the
-<
<
+		JXTA network. Most applications and services will instantiate their own peer groups using the Network Peer Group as a base.
->
>
+	JXTA network. Most applications and services will instantiate their own peer groups using the Network Peer Group as a base.
  P2P^?, Peer-to-Peer
 A decentralized networking paradigm in which distributed nodes,		or peers, communicate and work collaboratively to provide services.
 		agreed upon a common set of services.
 

 World Peer Group, PlatformGroup
 The most fundamental peer group within
-<
<
+		the JXTA network. This core peer group is generally responsible only for management of physical
->
>
+		the JXTA network. This core peer group is generally responsible only for management of physical
 		network connections, physical network (generally broadcast) discovery and physical network topology
-<
<
+		management. Applications generally do not interact with this group. May only include limited discovery, 
		publication, rendezvous and pipe services.
->
>
+		management. Applications generally do not interact with this group. May only include limited endpoint,
		resolver, discovery and rendezvous services.
  XML
 (From *Extensible Markup Language (XML) 1.0* ) :		Extensible Markup Language, abbreviated XML, describes		a class of data objects called XML documents and 		partially describes the behavior ofcomputer programs which process them.
-<
<
+-- MikeDuigou - 29 Feb 2004

<<O>> Difference Topic JxtaGlossary (3 - 29 Apr 2004 - Main.bondolo)

Line: 1 to 1

META TOPICPARENT	name="WebHome"

JXTA Glossary

Line: 59 to 59

specification is primarily used to access a module.

Network Peer Group: The base peer group for applications and services within the

Changed:

<
<

JXTA network. Most applications and services will instantiate their own peer groups using the Network Peer Group.

>
>

JXTA network. Most applications and services will instantiate their own peer groups using the Network Peer Group as a base.

P2P^?, Peer-to-Peer: A decentralized networking paradigm in which distributed nodes, or peers, communicate and work collaboratively to provide services.

Added:

>
>

Peer: A peer is any uniquely identifiable networked device which is capable of interacting with other network devices using standardized protocols.

Peer Group: A collection of peers that have a common set of interests and have agreed upon a common set of services.

<<O>> Difference Topic JxtaGlossary (2 - 02 Mar 2004 - Main.bondolo)

Line: 1 to 1

META TOPICPARENT	name="WebHome"

JXTA Glossary

Line: 58 to 58

can be multiple module specifications for a given module class. The module specification is primarily used to access a module.

Added:

>
>

Network Peer Group: The base peer group for applications and services within the JXTA network. Most applications and services will instantiate their own peer groups using the Network Peer Group.

P2P^?, Peer-to-Peer: A decentralized networking paradigm in which distributed nodes, or peers, communicate and work collaboratively to provide services.

Peer Group: A collection of peers that have a common set of interests and have agreed upon a common set of services.

Added:

>
>

World Peer Group, PlatformGroup: The most fundamental peer group within the JXTA network. This core peer group is generally responsible only for management of physical network connections, physical network (generally broadcast) discovery and physical network topology management. Applications generally do not interact with this group. May only include limited discovery, publication, rendezvous and pipe services.

XML: (From *Extensible Markup Language (XML) 1.0* ) : Extensible Markup Language, abbreviated XML, describes a class of data objects called XML documents and partially describes the behavior ofcomputer programs which process them.

Added:

>
>

-- MikeDuigou - 29 Feb 2004

<<O>> Difference Topic JxtaGlossary (1 - 01 Mar 2004 - Main.bondolo)

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="WebHome"

JXTA Glossary

Advertisement: JXTA's language-neutral metadata structures that describe peer resources such as peers, peer groups, pipes, and services. Advertisements are represented as XML documents.

Binding: An implementation of the Project JXTA protocols for a particular environment (e.g., the J2SE^? platform binding).

Codat: The combination of a content (commonly a document or file) and a JXTA ID.

Credential: A token used to uniquely identify the sender of a message; can be used to provide message authorization.

JXTA: JXTA is not an acronym, and in particular the "J"does not refer to Java. JXTA is a made up word coined by the project's original sponsor, Bill Joy. JXTA is derived from the word Juxtapose, as in side by side. It is a recognition that peer-to-peer is juxtaposed to client server or Web based computing -- what is considered today's traditional computing model.

JXTA Core Specification: The JXTA Core Specification consists of the required components and behaviours which are present in all conforming JXTA implementations. This includes the Peer Endpoint Protocol (PEP) and the Peer Resolver Protocol (PRP).

JXTA ID Format: A JXTA ID Format is a scheme for representing it IDs of JXTA entities. Each ID Format is identified by as sub-namespace of the URN namespace "jxta".

JXTA ID Type: A JXTA ID Type is describes the characteristics of JXTA IDs which refer to a particular sort of JXTA entity. Currently this includes peer groups, peers, codats, pipes, module classes, module specifications and module impelmentations, but may be extended to refer to other types of entities in the future or in specific implementations.

JXTA Standard Services: The JXTA Standard Services are optional JXTA components and behaviours. Implementations are not required to provide these services, but are strongly recommended to do so. This includes Peer Discovery Protocol (PDP), Peer Information Protocol (PIP), Pipe Binding Protocol (PBP) and Rendezvous Protocol (RVP).

Module: An abstraction used to represent any piece of "code" used to implement a behavior in the JXTA world. Network services are the mode common example of behavior that can be instantiated on a peer.

Module Class: Represents an expected behavior and an expected binding to support the module; is used primarily to advertise the existence of a behavior.

Module Implementation: The implementation of a given module specification; there may be multiple module implementations for a given module specification.

Module Specification: Describes a specification of a given module class; it is one approach to providing the functionality that a module class implies. There can be multiple module specifications for a given module class. The module specification is primarily used to access a module.

P2P^?, Peer-to-Peer: A decentralized networking paradigm in which distributed nodes, or peers, communicate and work collaboratively to provide services.

Peer Group: A collection of peers that have a common set of interests and have agreed upon a common set of services.

XML: (From *Extensible Markup Language (XML) 1.0* ) : Extensible Markup Language, abbreviated XML, describes a class of data objects called XML documents and partially describes the behavior ofcomputer programs which process them.

-- MikeDuigou - 29 Feb 2004

Topic JxtaGlossary . { View | Diffs r5 < r4 < r3 < r2 | More }

java.net RSS