Michael Koziarski wrote:
That is, setting a socket is the exception rather than the rule. For
most of the get-up-and-running apps I've seen, the socket isn't
necessary. Trying to set it is often an impediment to getting
started with Rails. But I suspect there may be downsides that led to
the d
> That is, setting a socket is the exception rather than the rule. For
> most of the get-up-and-running apps I've seen, the socket isn't
> necessary. Trying to set it is often an impediment to getting
> started with Rails. But I suspect there may be downsides that led to
> the decision to use a
+1 to comment out socket
On 3/4/06, Keegan Quinn <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 04, 2006 at 09:48:50AM -0700, Mike Clark wrote:
> > That is, setting a socket is the exception rather than the rule. For
> > most of the get-up-and-running apps I've seen, the socket isn't
> > necessary.
>
>
On Sat, Mar 04, 2006 at 09:48:50AM -0700, Mike Clark wrote:
> That is, setting a socket is the exception rather than the rule. For
> most of the get-up-and-running apps I've seen, the socket isn't
> necessary.
FWIW, this has been my experience as well.
--
Keegan Quinn <[EMAIL PROTECTED]>
C
