Sorry, the two emails were asynchronous. I read your response to that
email after sending the one below.
I would just like a detailed explanation of how Transactions work in
Castor. I don't know how to put it any simpler. I'd also like a detailed
technical explanation of how Castor caches, and how to properly use the
cache. What I'm asking might take you too long to write for simply
answering an question via email. I'd settle for a "best practice" for
using caching and transactions in Castor. Anthony's stuff just confused
me more.
Bruce, I feel like I'm being an ass about this. If I am, I'm sorry. I
would do fine just looking at the Castor code and figuring these things
out for myself. But, I don't have time to hack open every 3rd party
piece of code I'd like to integrate, all I want to know is the safe and
proper way to use/deploy. What I want to avoid is a client calling me up
saying their data is corrupted, the application is locking up (dead
lock), or anything else scary like that.
-ryan
On Thu, 2001-12-06 at 14:08, Bruce Snyder wrote:
> This one time, at band camp, Ryan Marsh said:
>
> RM>I'd like to understand how Transactions are handled in Castor. You can
> RM>also check out my other message to the list entitled "Beta
> RM>Documentation?"
> RM>
>
> Ryan,
>
> I answered your previous message titled Beta Documentation.
>
> However, I'm still unclear as to what you'd like to know about
> Castor's transactions. Again, what exactly would you like to know?
> Do you want to know about the locking modes or what?
>
> Bruce
>
> --
>
> perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
