diff options
| author | Pratik Naik <pratiknaik@gmail.com> | 2008-09-26 23:53:27 +0100 |
|---|---|---|
| committer | Pratik Naik <pratiknaik@gmail.com> | 2008-09-26 23:53:27 +0100 |
| commit | a7e529191de38fb39dd9350fb740898c581c8893 (patch) | |
| tree | be4b8634d2c4bcf60b1489c0bde4da9b1986724e /railties | |
| parent | b8036e847a99778ea832cb7961b1f8dd8f10a1a1 (diff) | |
| download | rails-a7e529191de38fb39dd9350fb740898c581c8893.tar.gz rails-a7e529191de38fb39dd9350fb740898c581c8893.tar.bz2 rails-a7e529191de38fb39dd9350fb740898c581c8893.zip | |
Change some more code -> source in code blocks
Diffstat (limited to 'railties')
| -rw-r--r-- | railties/doc/guides/actioncontroller/session.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/railties/doc/guides/actioncontroller/session.txt b/railties/doc/guides/actioncontroller/session.txt index b718770e63..50ed76e3ae 100644 --- a/railties/doc/guides/actioncontroller/session.txt +++ b/railties/doc/guides/actioncontroller/session.txt @@ -16,7 +16,7 @@ The default and recommended store, the Cookie Store, does not store session data If you need a different session storage mechanism, you can change it in the `config/environment.rb` file: -[code, ruby] +[source, ruby] ------------------------------------------ # Set to one of [:active_record_store, :sql_session_store, :drb_store, :mem_cache_store, :cookie_store] config.action_controller.session_store = :active_record_store @@ -26,7 +26,7 @@ config.action_controller.session_store = :active_record_store In your controller you can access the session through the `session` method. Session values are stored using key/value pairs like a hash: -[code, ruby] +[source, ruby] ------------------------------------------ class ApplicationController < ActionController::Base @@ -42,7 +42,7 @@ end To store something in the session, just assign it to the key like a hash: -[code, ruby] +[source, ruby] ------------------------------------------ class LoginsController < ApplicationController @@ -60,7 +60,7 @@ end To remove something from the session, assign that key to be `nil`: -[code, ruby] +[source, ruby] ------------------------------------------ class LoginsController < ApplicationController @@ -80,7 +80,7 @@ To reset the entire session, use `reset_session`. The flash is a special part of the session which is cleared with each request. This means that values stored there will only be available in the next request, which is useful for storing error messages etc. It is accessed in much the same way as the session, like a hash. Let's use the act of logging out as an example. The controller can set a message which will be displayed to the user on the next request: -[code, ruby] +[source, ruby] ------------------------------------------ class LoginsController < ApplicationController @@ -95,7 +95,7 @@ end The `destroy` action redirects to the application's `root_url`, where the message will be displayed. Note that it's entirely up to the next action to decide what, if anything, it will do with what the previous action put in the flash. It's conventional to a display eventual errors or notices from the flash in the application's layout: -[code, rhtml] +[source, ruby] ------------------------------------------ <!-- head, etc --> <body> @@ -114,7 +114,7 @@ This way, if an action sets an error or a notice message, the layout will displa If you want a flash value to be carried over to another request, use the `keep` method: -[code, ruby] +[source, ruby] ------------------------------------------ class MainController < ApplicationController |