On Jun 28, 5:47 pm, Mark Mandel <[email protected]> wrote:
> On Sun, Jun 28, 2009 at 6:39 PM, Elliott Sprehn <[email protected]> wrote:
>
> ...
>
> And a mechanism, to be able to switch between the credentials as neccessary,
> which is far more flexibly than just 'read', and 'write'.
>

The complexity is more than necessary and requires much more work than
just adding a read/write datasource.

Again your solution doesn't stop reads on the writing datasource if
some action that happens after your listener switches the thread
datasource.

This is not as simple as implementing a listener, it requires going
back and making sure all your code doesn't cause those incorrect reads
which is especially nasty if you have many listeners. Now you have to
think about which listeners happen when and what they do. And even
then that's not future proof since a listener from a third party for
validation that is added at a later date might cause reads on the
wrong datasource. You'd have to constantly be careful and double check
all the interactions.

I don't understand why you can't implement separate reading and
writing datasources and still allow your
setCurrentThreadReadingDatasource() method to exist.

Your solution has lots of obvious caveats that significantly reduce
the usefulness of the feature, and make it much more error prone. It's
far less likely to get used, especially properly, and again it's not a
drop in solution. You'd have to go back and double check every code
path to make sure you didn't cause reads on the wrong datasource.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to