[Bast-commits] r4386 - DBIx-Class/0.08/branches/replication_dedux/lib/DBIx/Class/Storage/DBI

jnapiorkowski at dev.catalyst.perl.org jnapiorkowski at dev.catalyst.perl.org
Wed May 14 18:57:57 BST 2008

Author: jnapiorkowski
Date: 2008-05-14 18:57:57 +0100 (Wed, 14 May 2008)
New Revision: 4386

documentation updates

Modified: DBIx-Class/0.08/branches/replication_dedux/lib/DBIx/Class/Storage/DBI/Replicated.pm
--- DBIx-Class/0.08/branches/replication_dedux/lib/DBIx/Class/Storage/DBI/Replicated.pm	2008-05-14 16:05:22 UTC (rev 4385)
+++ DBIx-Class/0.08/branches/replication_dedux/lib/DBIx/Class/Storage/DBI/Replicated.pm	2008-05-14 17:57:57 UTC (rev 4386)
@@ -43,16 +43,22 @@
 database, all read-type queries (SELECTs) go to the slave database.
 Basically, any method request that L<DBIx::Class::Storage::DBI> would normally
-handle gets delegated to one of the two attributes: L</master_storage> or to
-L</current_replicant_storage>.  Additionally, some methods need to be distributed
+handle gets delegated to one of the two attributes: L</read_handler> or to
+L</write_handler>.  Additionally, some methods need to be distributed
 to all existing storages.  This way our storage class is a drop in replacement
 for L<DBIx::Class::Storage::DBI>.
 Read traffic is spread across the replicants (slaves) occuring to a user
 selected algorithm.  The default algorithm is random weighted.
-TODO more details about the algorithm.
+=head1 NOTES
+The consistancy betweeen master and replicants is database specific.  The Pool
+gives you a method to validate it's replicants, removing and replacing them
+when they fail/pass predefined criteria.  It is recommened that your application
+define two schemas, one using the replicated storage and another that just 
+connects to the master.
 This class defines the following attributes.

More information about the Bast-commits mailing list