Of course the other option is - have 2 transferFactories, one for read, and one for write, with an application scoped cache.
That would work too ;o) Mark On Fri, Jun 26, 2009 at 4:11 AM, Dan Wilson <[email protected]> wrote: > > I've been thinking of horizontally scalling mysql and will be setting > up 2 servers, one will be the single point for writes, the other will > be the preferred point for reads. These two will be connected by > serial replication. > > Thus, i'll need to use seperate datasources for each machine and have > a way to use the correct data source for the specific operation. > Ideally, with a way to choose one of the boxes for reads. > > Can transfer support this as it stands? > > If not, what would a rough idea of effort be to add support for a user > defined getWritableDSN() and getReadableDSN()? > > Dan > > > > -- > “Come to the edge, he said. They said: We are afraid. Come to the > edge, he said. They came. He pushed them and they flew.” > > Guillaume Apollinaire quotes > > > > -- E: [email protected] T: http://www.twitter.com/neurotic W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
