Greg Beaver has this new posting on his blog today, giving "their explaination" as to why Chiara_PEAR_Server will not implement push-based mirroring.

While investigating unrelated code, I stumbled upon this article: http://www.manageability.org/blog/stuff/why-rest-part-3/view. The part I find most directly applicable to the question of how to implement mirroring in Chiara_PEAR_Server is quoted below:

"The push and pull methods both fail if the consumer isn't informed of a change in the producer. The difference however is this, which party holds the responsibility for ensuring compatibility?"

This is the primary reason that Chiara_PEAR_Server's interaction with mirrors will always be pull-based rather than push-based. In practical terms, this means that a Chiara_PEAR_Server-based primary site will never need to know about its mirrors [...] instead, the mirror will be responsible for pulling the new data from the primary site.

The Chiara_PEAR_Server is one of Greg's many projects, and provides channel server services for PEAR...