Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

removed$Id$

  • Loading branch information...
commit 39154be699eb1b889a4356c219976ed85f4f7cb6 1 parent 95377e8
@belaban authored
Showing with 0 additions and 41 deletions.
  1. +0 −1  doc/NullDestAddresses.txt
  2. +0 −1  doc/NullingSrcAddresses.txt
  3. +0 −1  doc/PerformanceNotes.txt
  4. +0 −1  doc/ProtocolReentrancy
  5. +0 −1  doc/ReleaseNotes-2.11.txt
  6. +0 −1  doc/bugs/Digest.txt
  7. +0 −1  doc/bugs/MergeProblem.txt
  8. +0 −1  doc/design/AUTH.txt
  9. +0 −1  doc/design/Bundling.txt
  10. +0 −1  doc/design/CLOUD_TCP.txt
  11. +0 −1  doc/design/ConcurrentConnectionEstablishment.txt
  12. +0 −1  doc/design/ConcurrentStack.txt
  13. +0 −1  doc/design/ConcurrentStartupTest.txt
  14. +0 −1  doc/design/DataCenterReplication.txt
  15. +0 −1  doc/design/FILE_PING.txt
  16. +0 −1  doc/design/FLUSH.txt
  17. +0 −1  doc/design/FLUSH2.txt
  18. +0 −1  doc/design/FlowControl.txt
  19. +0 −1  doc/design/GossipRouterChanges-1.8.txt
  20. +0 −1  doc/design/LargeClusters.txt
  21. +0 −1  doc/design/LargeMessages.txt
  22. +0 −1  doc/design/LogicalAddresses.txt
  23. +0 −1  doc/design/MERGE.new.txt
  24. +0 −1  doc/design/MERGE4.txt
  25. +0 −1  doc/design/MERGE_View_Separation.txt
  26. +0 −1  doc/design/Multiplexer.txt
  27. +0 −1  doc/design/NAKACK.txt
  28. +0 −1  doc/design/PartialStateTransfer.txt
  29. +0 −1  doc/design/Reincarnation.txt
  30. +0 −1  doc/design/ReliableViewInstallation.txt
  31. +0 −1  doc/design/SCOPE.txt
  32. +0 −1  doc/design/SEQUENCER.txt
  33. +0 −1  doc/design/STABLE.txt
  34. +0 −1  doc/design/SimpleFlowControl.txt
  35. +0 −1  doc/design/StreamingStateTransfer.txt
  36. +0 −1  doc/design/TestNG.txt
  37. +0 −1  doc/design/TransportNextGen
  38. +0 −1  doc/design/UNICAST.new.txt
  39. +0 −1  doc/design/UNICAST.txt
  40. +0 −1  doc/design/UNIFORM.txt
  41. +0 −1  doc/design/ViewHandling.txt
View
1  doc/NullDestAddresses.txt
@@ -2,7 +2,6 @@
Nulling of destination addresses for optimized marshalling
==========================================================
-Version: $Id: NullDestAddresses.txt,v 1.2 2005/08/26 11:06:37 belaban Exp $
Author: Bela Ban
Date: Aug 26 2005
View
1  doc/NullingSrcAddresses.txt
@@ -3,7 +3,6 @@ Loopback adaptor issues on Windows
----------------------------------
JIRA: http://jira.jboss.com/jira/browse/JGRP-79
-Version: $Id: NullingSrcAddresses.txt,v 1.1 2005/05/19 07:57:46 belaban Exp $
On Windows, when a loopback adaptor is created, we can associate multiple (virtual) IP
addresses with it, e.g. 10.0.0.1 and 10.0.0.2.
View
1  doc/PerformanceNotes.txt
@@ -2,7 +2,6 @@
Check list for performance tuning (mainly gige)
===============================================
-Version: $Id: PerformanceNotes.txt,v 1.1 2006/08/15 08:23:33 belaban Exp $
Author: Bela Ban, Eric
For the transmit queue:
View
1  doc/ProtocolReentrancy
@@ -1,6 +1,5 @@
Author: Bela Ban
-Version: $id$
A typical protocol in JGroups can be assured that only up() and down() methods can be called concurrently,
however up() and up() methods, and down() and down() methods cannot be called concurrently. This is due
View
1  doc/ReleaseNotes-2.11.txt
@@ -4,7 +4,6 @@ Release Notes JGroups 2.11
==========================
-Version: $Id: ReleaseNotes-2.11.txt,v 1.3 2010/10/29 11:48:28 belaban Exp $
Author: Bela Ban
JGroups 2.11 is API-backwards compatible with previous versions (down to 2.2.7).
View
1  doc/bugs/Digest.txt
@@ -3,7 +3,6 @@ Digest on view changes
======================
Author: Bela Ban
-Version: $Id: Digest.txt,v 1.1 2006/01/26 09:23:16 belaban Exp $
With STATE_TRANSFER we disable message garbage collection with SUSPEND_STABLE for the duration of the state transfer
View
1  doc/bugs/MergeProblem.txt
@@ -4,7 +4,6 @@ Merge problem in GMS/MERGE2
===========================
Author: Bela Ban
-Version: $Id: MergeProblem.txt,v 1.1 2006/01/27 14:46:11 belaban Exp $
Symptom: first merge works, subsequent merges don't work
Unit test: MergeStressTest
View
1  doc/design/AUTH.txt
@@ -4,7 +4,6 @@ Design of authentication protocol (AUTH)
========================================
Author: Roland Raez, Bela Ban, Chris Mills
-Version: $Id: AUTH.txt,v 1.1 2006/01/27 14:46:12 belaban Exp $
Goal: to prevent random members from joining a group. Members have to pass authentication
to join a group, otherwise they will be rejected
View
1  doc/design/Bundling.txt
@@ -4,7 +4,6 @@
Message bundling
================
-// Version: $Id: Bundling.txt,v 1.1 2006/01/27 14:46:12 belaban Exp $
// Author: Bela Ban
Init:
View
1  doc/design/CLOUD_TCP.txt
@@ -4,7 +4,6 @@ Changes to TCP to make it scale better in a cloud
=================================================
Author: Bela Ban
-Version: $Id: CLOUD_TCP.txt,v 1.5 2010/07/29 06:57:25 belaban Exp $
Problem:
View
1  doc/design/ConcurrentConnectionEstablishment.txt
@@ -1,6 +1,5 @@
-// Version: $Id: ConcurrentConnectionEstablishment.txt,v 1.3 2007/09/19 12:42:43 belaban Exp $
// Author: Bela Ban
View
1  doc/design/ConcurrentStack.txt
@@ -4,7 +4,6 @@ Concurrent stack
================
Author: Bela Ban
-Version: $Id: ConcurrentStack.txt,v 1.1 2006/12/27 10:02:04 belaban Exp $
JIRAs:
http://jira.jboss.com/jira/browse/JGRP-180 (harden stack)
http://jira.jboss.com/jira/browse/JGRP-181 (concurrent stack)
View
1  doc/design/ConcurrentStartupTest.txt
@@ -3,7 +3,6 @@ Notes regarding ConcurrentStartupTest
=====================================
// Author: Bela Ban
-// Version: $Id: ConcurrentStartupTest.txt,v 1.2 2006/05/20 22:02:12 belaban Exp $
The unit test org.jgroups.tests.ConcurrentStartupTest simulates multiple nodes in a cluster being started at the same
View
1  doc/design/DataCenterReplication.txt
@@ -3,7 +3,6 @@ Replication between data centers
================================
Author: Bela Ban
-Version: $Id: DataCenterReplication.txt,v 1.10 2010/11/08 12:02:53 belaban Exp $
We have data centers in New York (NYC) and San Francisco (SFO). The idea is to replicate traffic from NYC to SFO
asynchronously. In case of a site failure of NYC, all clients can be switched over to SFO and continue working with
View
1  doc/design/FILE_PING.txt
@@ -4,7 +4,6 @@ Design of FILE_PING
===================
Author: Bela Ban
-Version: $Id: FILE_PING.txt,v 1.3 2009/04/24 07:17:56 belaban Exp $
Goal
View
1  doc/design/FLUSH.txt
@@ -3,7 +3,6 @@ FLUSH protocol for default stack
================================
Author: Bela Ban
-Version: $Id: FLUSH.txt,v 1.11 2007/11/08 14:34:52 vlada Exp $
See http://jira.jboss.com/jira/browse/JGRP-82
Overview
View
1  doc/design/FLUSH2.txt
@@ -4,7 +4,6 @@ FLUSH2 design
=============
Author: Bela Ban
-Version: $Id: FLUSH2.txt,v 1.8 2009/03/02 07:29:19 belaban Exp $
Prerequisites:
- A flush is always started and stopped by the *same* member, both for joins and state transfer
View
1  doc/design/FlowControl.txt
@@ -1,4 +1,3 @@
-// Version: $Id: FlowControl.txt,v 1.1 2006/01/27 14:38:35 belaban Exp $
// Author: Bela Ban
View
1  doc/design/GossipRouterChanges-1.8.txt
@@ -3,7 +3,6 @@
Changes to GossipRouter in 2.8
==============================
Author: Bela Ban
-Version: $Id: GossipRouterChanges-1.8.txt,v 1.9 2009/07/06 08:55:06 belaban Exp $
Motivation
View
1  doc/design/LargeClusters.txt
@@ -4,7 +4,6 @@ Considerations for large clusters
=================================
Author: Bela Ban
-Version: $Id: LargeClusters.txt,v 1.3 2010/09/30 07:47:20 belaban Exp $
JIRA: https://jira.jboss.org/browse/JGRP-100
View
1  doc/design/LargeMessages.txt
@@ -3,7 +3,6 @@ Large messages in large clusters
================================
Author: Bela Ban
-Version: $Id: LargeMessages.txt,v 1.3 2009/05/15 10:39:35 belaban Exp $
Requirements
------------
View
1  doc/design/LogicalAddresses.txt
@@ -4,7 +4,6 @@ Logical addresses
=================
Author: Bela Ban
-Version: $Id: LogicalAddresses.txt,v 1.13 2009/04/09 09:11:32 belaban Exp $
JIRA: https://jira.jboss.org/jira/browse/JGRP-129
The address chosen by each node is essentially the IP address and port of the receiver socket. However, for the
View
1  doc/design/MERGE.new.txt
@@ -3,7 +3,6 @@ New merging algorithm
=====================
Author: Bela Ban
-Version: $Id: MERGE.new.txt,v 1.2 2009/04/27 12:06:28 belaban Exp $
JIRAs: https://jira.jboss.org/jira/browse/JGRP-948, https://jira.jboss.org/jira/browse/JGRP-940
Goal
View
1  doc/design/MERGE4.txt
@@ -3,7 +3,6 @@ MERGE4
------
Author: Bela Ban
-Version: $Id: MERGE4.txt,v 1.3 2009/06/09 11:47:35 belaban Exp $
JIRA: https://jira.jboss.org/jira/browse/JGRP-937
Goal
View
1  doc/design/MERGE_View_Separation.txt
@@ -4,7 +4,6 @@ Separation of merges from view handling
=======================================
Author: Bela Ban
-Version: $Id: MERGE_View_Separation.txt,v 1.6 2009/08/24 13:55:38 belaban Exp $
JIRA: https://jira.jboss.org/jira/browse/JGRP-1009
Goal:
View
1  doc/design/Multiplexer.txt
@@ -4,7 +4,6 @@ Multiplexing functionality
===========================
Author: Bela Ban
-Version: $Id: Multiplexer.txt,v 1.18 2006/07/11 12:36:37 belaban Exp $
JIRA: http://jira.jboss.com/jira/browse/JGRP-119, http://jira.jboss.com/jira/browse/JGRP-112
Overview
View
1  doc/design/NAKACK.txt
@@ -6,7 +6,6 @@ Design of new NAKACK with only 1 retransmission table
Author: Bela Ban
Date: April 3, 2007
JIRA: http://jira.jboss.com/jira/browse/JGRP-281
-Version: $Id: NAKACK.txt,v 1.9 2007/04/19 21:01:17 belaban Exp $
View
1  doc/design/PartialStateTransfer.txt
@@ -1,5 +1,4 @@
-// Version: $Id: PartialStateTransfer.txt,v 1.1 2006/01/27 14:46:12 belaban Exp $
// Author: Bela Ban
Partial state transfer
View
1  doc/design/Reincarnation.txt
@@ -4,7 +4,6 @@ Problems with reincarnation
===========================
Author: Bela Ban
-Version: $Id: Reincarnation.txt,v 1.1 2006/01/27 14:46:12 belaban Exp $
JIRA: http://jira.jboss.com/jira/browse/JGRP-130
The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
View
1  doc/design/ReliableViewInstallation.txt
@@ -3,7 +3,6 @@ Reliable view installation
==========================
Author: Bela Ban
-Version: $Id: ReliableViewInstallation.txt,v 1.1 2006/01/27 14:46:12 belaban Exp $
The default stack sees view as just messages; a view multicast is retransmitted until the sender is excluded because
it left or crashed. However, this behavior can lead to problems described below. The problems occur when a view
View
1  doc/design/SCOPE.txt
@@ -4,7 +4,6 @@ Implementation of the SCOPE protocol
====================================
Author: Bela Ban
-Version: $Id
Scopes allow for concurrent delivery of messages sent by the same sender, without having to resort to OOB.
View
1  doc/design/SEQUENCER.txt
@@ -5,7 +5,6 @@ Design of SEQUENCER, a total order protocol using a sequencer
Author: Bela Ban
Date: Dec 29 2005
-Version: $Id: SEQUENCER.txt,v 1.3 2009/11/20 10:41:44 belaban Exp $
Motivation
View
1  doc/design/STABLE.txt
@@ -4,7 +4,6 @@ STABLE
Author: Bela Ban
Date: May 29 2007
-Version: $Id: STABLE.txt,v 1.2 2007/05/31 09:56:58 belaban Exp $
Goal: to purge messages delivered by all members
View
1  doc/design/SimpleFlowControl.txt
@@ -1,5 +1,4 @@
-// Version: $Id: SimpleFlowControl.txt,v 1.2 2007/01/05 15:51:58 belaban Exp $
// Author: Bela Ban
View
1  doc/design/StreamingStateTransfer.txt
@@ -4,7 +4,6 @@ Streaming state transfer
Author: Vladimir Blagojevic
Date: July 2006
-Version: $Id: StreamingStateTransfer.txt,v 1.4 2006/07/31 16:12:20 vlada Exp $
Overview
View
1  doc/design/TestNG.txt
@@ -4,7 +4,6 @@ Migration from JUnit to TestNG
==============================
Author Bela Ban
-Version: $Id: TestNG.txt,v 1.17 2008/04/18 09:13:12 belaban Exp $
Goals
-----
View
1  doc/design/TransportNextGen
@@ -4,7 +4,6 @@ Transport Next Generation
-------------------------
Author: Bela Ban
-Version: $Id: TransportNextGen,v 1.1 2009/06/30 11:57:16 belaban Exp $
The next version of the transport (org.jgroups.protocols.TP) should be NIO based: TP has an NIO selector, and subclasses
such as TCP or UDP only register NIO channels with TP. For example, UDP would create 2 NIO channels, a unicast and a
View
1  doc/design/UNICAST.new.txt
@@ -4,7 +4,6 @@ New UNICAST design
(see UNICAST.txt for the old design)
Author: Bela Ban
-Version: $Id: UNICAST.new.txt,v 1.6 2009/04/29 10:38:46 belaban Exp $
Motivation
----------
View
1  doc/design/UNICAST.txt
@@ -4,7 +4,6 @@ UNICAST and membership
Author: Bela Ban
Date: Aug 10 2006
-Version: $Id: UNICAST.txt,v 1.3 2006/08/11 07:55:17 belaban Exp $
Sending a unicast message to P
View
1  doc/design/UNIFORM.txt
@@ -3,7 +3,6 @@ Uniform message delivery
========================
Author: Bela Ban
-Version: $Id: UNIFORM.txt,v 1.2 2006/04/25 03:00:31 belaban Exp $
Definition
View
1  doc/design/ViewHandling.txt
@@ -4,7 +4,6 @@ New view handling
=================
Author: Bela Ban
-Version: $Id: ViewHandling.txt,v 1.1 2006/01/27 14:46:12 belaban Exp $
Problem:
Merge, join and leave requests need to handled in the order in which they arrive. Currently,
Please sign in to comment.
Something went wrong with that request. Please try again.