[server] instead of apache?

[Tony]

Well I'm running Rails and its blazing fast as long as apache is off. Turning apache on slows a page down to 10~15 seconds, which is redicilous.

Now the tradeoff is that without apache I can no longer connect to the server outside of the localhost:port . Is there an alternative for vertual hosting that would point to the Rails directory when connected to over the network?

[rizzix]

how does rails work if apache is off?... either way... one thing is for sure.. Ruby is hell slow anyways specially the ruby regex engine.. but u say that apache affects it eh?

[wtd]

rizzix wrote:

how does rails work if apache is off?... either way... one thing is for sure.. Ruby is hell slow anyways specially the ruby regex engine.. but u say that apache affects it eh?

Rails has it's own webserver, built solely with Ruby. Rails defaults to using this.

Yes, Ruby's regex engine is slow. That's why it's being rewritten. There's nothing inherently "slow" about Ruby itself, though. On a mainstream machine it's limited primarily by input and output operations, as with most any other programming language.

[Tony]

problem is that computerName:port_number does not respond, although localhost:port_number does..

what about ipaddress:port_number instead of computerName:port_number


sorry, blade edited this ... explanation below

[rizzix]

hmm... i have no idea

wanna switch? there's always ZOPE.

[wtd]

rizzix wrote:

hmm... i have no idea

wanna switch? there's always ZOPE.

Ugh... I've dealt with Zope. That was not pleasant.

[Blade]

tony wrote:

.. problem is that computerName:port_number does not respond, although localhost:port_number does..

what about ipaddress:port_number instead of computerName:port_number

edit: awwww crap, sorry i didnt know i could edit posts in here until now, i thought i hit "quote"

[Tony]

Blade wrote:

what about ipaddress:port_number

nope.
localhost or no deal. This is not cool