Bug 490986

Summary:	Errors describing Federation
Product:	Red Hat Enterprise MRG	Reporter:	William Henry <whenry>
Component:	Messaging_Programming_Reference	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Frantisek Reznicek <freznice>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.1	CC:	esammons, jonathan.robie, mhideo
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-14 05:22:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description William Henry 2009-03-18 19:25:43 UTC

Description of problem:

Under "Push and pull routes" the following sentence does not make sense:
"Dynamic routes are always pull routes. Static routes are normally pull routes but if the src-local option is used when creating or deleting a route, it will become a pull route instead."
The instead implied a change that doesn't occur - e.g. normally pull .... push route instead".


Also the following sentence (paragraph before) seems to have a typo:
"When the source broker is configures and pushes the information to the destination broker, it is a push route."



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jonathan Robie 2009-03-19 19:46:09 UTC

Removed the entire section. Replaced with the following paragraph:

<para>
Routes can be configured from either the source broker or the destination broker. In most cases, they are configured from the source broker. Sometimes it is more convenient to configure links and routes from the destination broker. For instance, if brokers are co-resident with data sources, each source can be configured to send data to the central broker.
</para>

The terminology was heavyweight and confusing, and did not make it easier to explain what is said above. And the terminology was not used in the rest of the document.

Consulted with Ted, who has signed off on the change.