One of our developers had enough luck to see new Google design which is pretty simple and clean.
Sure he made few screen-shots and we glad to share it now with All World.
And surely we hope Google will approve it for mass use and tomorrow we will see it on almost any browser in the World.
Comments are welcome!
Ruby on Rails is a great framework that still luck some common features, among them: multi-domain support.
Here I will describe fast solution that doesn’t work for every browser and another one that do the work.
Ok, you did your homework and google something like ‘ruby on rails multi-domain’.
Very often provided solution:
edit environment.rb
1 | config.action_controller.session = {:domain => '.mydomain.com'} |
With that parameter Rails always read cookies from same domain. In real some browsers forbid for applications to read cookies from other domain due to insecurity of that operation. And as Mozilla Firefox in set of browsers that forbid that we just need another solution.
Now it’s clear that we should implement necessary functionality other way.
environment.rb:
1 | config.action_controller.session_store = :active_record_store |
and then execute rake task that create necessary DB migration:
1 | rake db:sessions:create |
Apply it with: rake db:migrate.
environment.rb:
1 2 3 4 5 6 7 8 9 | require "rubygems" require "active_support" config.action_controller.session = { :session_key => '_myapp_session_id', # session identification key :secret => '89sHslddfsd98klasdKd', # hash code of session generator(make it random and longer) :cookie_only => false, :expire_after => 1.week, # TTL (time to live) } |
application_controller.rb:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | before_filter { |controller| opts = controller.request.session_options key = opts[:key] # use session ID if it's passed if controller.params[key] # session initialization with old ID controller.session[:nothing] opts[:id] = controller.params[key] controller.request.session_options = opts # session initialization with new ID controller.session[:nothing] end } |
We need to pass session ID as parameter when user change domain name, and within domain we still use cookie.
1 | “#{request.session_options[:key]}” => request.session_options[:id] |
It’s wise to use session initialization before request.session_options[:id] invocation due to Rails use lazy loading, and session can be uninitialized.
Use something like: session[:nothing].
Pay attention that information that Rails get from cookie has bigger priority, and so if you have some parameter in cookie Rails will use it firstly.
Note:
An attacker can still steal you session ID by sniffing the network, or exploiting javascript, he/she gets the value from the cookie itself. If you care about security so much just use HTTPS.
Today even great application can die alone .. world has too many great applications.
me
Do you know what software development company sell?
Not just some abstract peace of software but application that can solve customer’s problems .. we should understand what customer wants from the application, what tasks he/she wants to solve with application.
We provide to customer our vision and suggest technology/platform/approach, customer provide ideas/plans/limitations .. together we will end with some satisfied result. But what then?
Then as usual we get our money and leave customer alone with his application.
We should give business advices that can bring closer customer’s target.
Client can take them or not but part of our work is to give ones. Customers see that we care, that help to build better relationship and get great satisfaction .. we make great applications that work!
Everybody who works with ruby on rails more then month knows at least 2 things:
it’s great framework, but can’t handle multiple requests simultaneously due to it still doesn’t use threads.
As scalability is common issue, rubyonrails site wiki provides full set of solutions:
[http://wiki.rubyonrails.org/#deployment_stacks]
But we as fast solution will use great OpenBSD pf (Packet Filter) that capable to do many cool things.
First issue is standard mongrail cluster that can start several instances of mongrail can only create them on one IP with different ports, and pf can’t distribute requests among different ports on same IP.
Here we can create 2 simple scripts that start and destroy server instances:
# cat start.sh
1 2 3 4 5 6 7 8 9 10 | count=1 for ip in 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5 do mongrel_rails start -e production -d --user myapp --group myapp --chdir /var/www/railsdocs/myapp \ --address ${ip} \ --pid /var/www/railsdocs/myapp/tmp/pids/mongrel.${count}.pid \ --log /var/www/railsdocs/myapp/log/mongrel.${count}.log count=$(($count + 1)) done |
# cat stop.sh
1 2 3 4 5 | for instance in {1..5} do mongrel_rails stop --wait 3 --chdir /var/www/railsdocs/myapp \ --pid /var/www/railsdocs/myapp/tmp/pids/mongrel.${instance}.pid end |
And we need to enable pf:
#/etc/rc.conf.local
1 2 | pf=YES #pflogd_flags= # add more flags, ie. "-s 256" |
add one string to configuration file for load distribution:
#/etc/pf.conf
1 2 | rdr pass log on re0 proto tcp from any to SOME_IP port 80 -> {10.0.0.1, 10.0.0.2, 10.0.0.3, 10.0.0.4, 10.0.0.5 } port 3000 round-robin |
check work with:
# pfctl -s nat
monitor with:
tcpdump -n -e -ttt -i pflog0
for more info on pf:
http://www.openbsd.org/faq/pf/
man pf.conf (especially ‘TRANSLATION’ and ‘POOL OPTIONS’ sections)
Then when you see you need more advanced solution for load distribution you can install haproxy.
Check it with [http://www.openbsd.org/4.5_packages/i386/haproxy-1.3.15.7.tgz-long.html]
“Be the change you want to see in the world.”
Mahatma Gandhi, Indian political and spiritual leader (1869 – 1948)
There are a lot of twitter directories on Internet today. Here I would want to check few most popular ones and provide our look on good directory.
1. plain list of categories
There is a number of categories on top page, user select one category, and browse all members in that category.
example from: [http://justtweetit.com/]
disadvantages:
a. enormous list of categories on main page.
b. cutting the list of categories creates too broad categories where too many entries are placed.
2. tags for naming of entries
For every entry user can provide number of tags, then users can select appropriate tag.
In theory user has ability to select most narrow meaning and thereby limit number of entries.
example from: [http://wefollow.com/twitter/tags/]
disadvantages:
a. there are still too broad tags like ‘celebrity’ with enormous amount of entries.
b. number of tags, so it is hard for user to select most narrow tag.
3. search engine style
Like in search engine user provides search term, and system search for similar entries.
example from: [http://twitdir.com/]
disadvantages:
a. user should know twitter name.
And if so user can use build-in twitter search [http://search.twitter.com]. But what if he/she wants to find for example pop style singer? Then user needs directory again!
All current directories provide possibility to any user to add himself/herself and so suffer from spammers and common(uninterested) users. There should be some quality criteria and some administrators that ensure continues quality of twitter IDs and correctness of provided information.
As it is money consuming tactic directory should make some money to cover costs or use open-source model where authorized users can check entities as it works in DMOZ directory [http://www.dmoz.org/help/become.html]
After some discussions within our company we have decided finally to create our own directory of twitter users.
We are taking into account disadvantages of current directories, and so our directory:
*has tree structure to reduce complexity, and size of categories
*uses moderators that ensure quality of twitter IDs before they add them.
Start exploration at: [http://twitwho.net].
Of course there is unlimited ways to improve everything, and so we are open to any suggestions and complains:
helion-prime’s twitter: [http://twitter.com/helionprime]
twitwhohq’s twitter: [http://twitter.com/twitwhohq]