Hi Paul, please see below:
On 9/11/07, Paul K. [email protected] wrote:
You didn’t mention in your post the “alternative” view - only that you
believe its great but with no counter argument to the points I raised.
Your general tone was that there was something hidden and that the
docs don’t tell the truth about the DRb requirement. That’s just
false. The top page of the doc says to use DRb in production
Single point of failure might be the only valid point you make, but
people are typically using monit to make sure that if the process
fails, it automatically restarts. (That’s what we do, and it works
Gem V plugin is always going to rage, I simply can’t get the plugin to
work with a svn:// url so I don’t have the option to use it, which means
I can’t run aaf at all because I have to have a basic cluster because
rails requires it! As I said in my post if the gem is going to be
published it should come with the necessary tools to get a Drb server
started, it seems like a simple enough change (I hope) and one that will
allow me to reenable my ferret support in my app.
Have you tried using piston? That’s a great way to get plugins for
Rails, and it does support the svn:// URL:
As for rejection as spam I don’t know what is going wrong there, I don’t
even have the spam filter turned on, are you doing the maths question?
I did – several times. Each time the message said something like
“your post has been flagged by our spam protection and will not be