From: Gaivs <julio.freitas@msn.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Rack's Arquitetura
Date: Wed, 2 May 2012 20:06:49 -0700 (PDT) [thread overview]
Message-ID: <69f7eb0b-fe77-407c-9e4b-ab76b6541d7f@m15g2000vbh.googlegroups.com> (raw)
Hello,
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
reply other threads:[~2012-05-03 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69f7eb0b-fe77-407c-9e4b-ab76b6541d7f@m15g2000vbh.googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).