* Rack's Arquitetura
@ 2012-05-03 3:06 Gaivs
0 siblings, 0 replies; only message in thread
From: Gaivs @ 2012-05-03 3:06 UTC (permalink / raw)
To: Rack Development
I am doing a study about ruby's architectures of programs. I am
specially looking for digressions on architecture.
I wish this isn't an embarrassing question, but I want to know the
architectural failures of Hack.
Studying the source code I found on rack/handler/mongrel.rb, between
lines 19 and 36. These lines and make URL mapping right on this layer
that have to be a facade server / application, crosscutting the
server.rb module. Can you confirm this affirmative?
And, can you point errors in the hack's architecture? This means,
basically the places where an object that access class of a module
that they should not do.
To be clear, my intent isn't to offend saying the implementation is
wrong, probably you made this for a sake of performance. But I need
this for my work of mastery.
Any help is very useful. Very thanks
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-05-03 6:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-03 3:06 Rack's Arquitetura Gaivs
Code repositories for project(s) associated with this inbox:
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).