New site built using Ruby on Rails

[Kirk Haines]

I am amazed at how fast ruby is at processing the requests. I come
from a J2EE background where the mantra was "CGI is slow", and so I
was amazed when I see ruby processing requests FASTER than a
comparable J2EE setup!

Oh, I agree! When I see .0035 second response times from a single processor
midrange linux box for 9k pages with modest dynamic content (and no content
caching), I am pleased. This is also under lighttpd with a fastcgi transport
layer. Ruby makes me smile. When I implement a caching dispatcher,
cacheable pages will become blazingly fast. At least in this sphere of work,
as I said last week, Ruby is plenty fast.


Kirk Haines

 

[Kirk Haines]

Any ideas on how to have a full-blown Ajax site that is "googlable" ?

I think it probably just boils down to making sure that the google spider can
get to any of the pages you want it to be able to reach without having to
execute any JS. I wonder if one could embed a set of links into a page that
are essentially there exclusively for spiders to find? i.e. in your JS
heavy, AJAX heavy page, they are completely hidden from a normal user's view,
but to a spider walking the page content, they see them?


Kirk Haines

 

[Devin Mullins]

I wonder if one could embed a set of links into a page that
are essentially there exclusively for spiders to find? i.e. in your JS
heavy, AJAX heavy page, they are completely hidden from a normal user's view,
but to a spider walking the page content, they see them?

Through CSS, we have display:none and visibility:hidden (which is
invisible, but affects flow). There are probably other tricks I don't
know about.

Devin