>> require ‘rubygems’
=> true
>> require ‘json’
=> true
>> JSON.unparse({“a”=>”b”})
=> “{\”a\”:\”b\”}”
>> require ‘active_support’
=> true
>> JSON.unparse({“a”=>”b”})
NoMethodError: undefined method `[]‘ for #
from /var/lib/gems/1.8/gems/activesupport-2.3.4/lib/active_support/json/encoders/hash.rb:45:in `as_json’
from /var/lib/gems/1.8/gems/activesupport-2.3.4/lib/active_support/json/encoders/hash.rb:34:in `to_json’
from /var/lib/gems/1.8/gems/json-1.1.9/lib/json/common.rb:183:in `unparse’
from (irb):5
>>

That looks nice. You’re right, it is more succinct.

And thanks for making me think more about it–I noticed a bug in my code when I read your post, and I think my bug made its way to your reply too. I’ve corrected it in the post above. I was originally using /@(.+)/ as the regular expression but that rewrites URLs that have an @ sign in the middle. I changed it to %r{/@(.+)} (inserted a slash at the front and used %r to avoid having to escape the slash).

I’m guessing the same thing would work in Rack::Rewrite.

Brian, Rack::Rewrite has a development branch that will allow you to do everything that Refraction does more succinctly.

As far as your example above, it’s actually simpler with Rack::Rewrite (http://github.com/jtrupiano/rack-rewrite ):

    config.middleware.insert_before(Rack::Lock, Rack::Rewrite) do
      rewrite /@(.+)/, "/users/$1"
    end

Rails::logger.info “\n\nStarting #{name}\n#{‘-’ * (9 + @name.length)}\n”

Good stuff. Here is the RESTful syntax:

 link_to_seo_remote(event.name, { :update => "#{dom_id(event)}_detail", :url => event_path(event), :method=>:get, :complete => visual_effect(:slide_down, "#{dom_id(event)}_detail") } )

Many thanks.

Did I mention that I love Rails?

http://http//www.infoq.com/presentations/straw-yellowpages
=>
http://www.infoq.com/presentations/straw-yellowpages

I would suggest learning to sail a boat. If you can sail a boat you can travel the seven seas indifinately, avoiding zombies and raiding coastal towns like a pirate for supplies! Yuo dont even need to own a boat, just steal it from a marina like in Dawn of the Dead.

First: where ever you go, you will need transportation, food, and a good hiding location. Last time I checked there was 6.5 billion people on earth so 2 weeks of food or hiding of roofs ain’t gonna cut it. My plan is to get to the SAMS club near my house. If you ever been in one it’s a fotress. Food and supplies surrounded by concrete. Once your in find the manager on duty and explain the situation. Ask for the keys and codes to everything. Tell them to grab their families and you will basicly protect the fort. Once in you have to block off all entrances with the tires in the tire section. Stack until you fill the glass doorway area. Several walls of tower will keep them out along with “food travelers” (the unprepared traveling looking for new food spots ) make sure the vechicles you brought are in the garage area. Leave an emergency car in the trucking area in the back (backup backup plan). Once you’ve checked all doors and all weak points in your fortress. Begin the second phase which is creating a system of smaller areas within your compound. Try to create more block offs around the store. Using the pallets of products make walls and “zones”. Also SAMS has rows and rows of product. Create a “treehouse system between each row. In emergency
situations the floor is no longer safe. The treehouse should have food for living and ways to the outside car need to be possible from the roof. If you aren’t compromised live your walls with couches,food, tv, secruity, batteries, generators. Use the perishable foods or frozen foods first. Use a grill or the microwaves to cook. Everyone should sleep in the treehouse assuming you were able to save your friends and family. If the zombies aren’t elimated or die of starvation. Plan to spend the next 6 years there. So create democracy or a leader. Also plan for “food travelers”. Because there is no government anarchy is everywhere. People will use survival of the fittest alot. People will come for your fortress so be prepared to defend it from zombies and other people.

Of course if you wake up and it’s too late to do any of this. Your already in the stage where it’s outside right now. Stay in your homes and block off your doors. If you live on the second floor of the apartment destroy the stairs. Your gonna be here until you die. Which will be in 6 months because there is no food.

Unification is more general than assignment. Assignment requires the left hand side to be a single variable. Unification, at least in most languages that support it, allows both sides to be arbitrary patterns, where any unbound dataflow variable in one pattern can be bound to a corresponding value in the other. This is explained well in the book ‘Concepts, Techniques and Models of Computer Programming’. (I don’t know whether this particular implementation supports patterns on both sides.)

“Speaking of debugging, if the debugger tries to show you the value of a Dataflow variable that hasn’t yet been assigned, the debugger thread itself will be put to sleep.”

That’s unfortunate. Ideally the debugger would just show that the variable is unbound (as it does in Mozart/Oz, and most other systems that support dataflow variables).

[...] if you can only assign a value when you declare a variable, obviously it will only be assigned once. [...]

In Erlang, there is no variable assignment, it’s actually a pattern match that’s going on and as a result of the match, the variable gets “bounded” to the result which is fundamentally different from assignment. Secondly, Variables can be declared and not bounded, these are termed “unbounded variables”

[...] Erlang handles it by heavy use of the stack and threads, so whenever you need a new value you call a function (which spawns a thread) and the function declares a new variable, assigning the new value to it. So there’s a lot of copying of values. [...]

Erlang is stack-less (which makes their tco easier to implement).. Secondly, Erlang doesn’t create a thread when you spawn/1, it’s a lightweight process and fundamentally different from a thread. I know what you are trying to say but care must be taken since you are trying to validate a point based on false statements.

Thanks for the info on this gem! I will definitely check it out as I feel that the only way to go forward from here on in is to make the switch to immutable state.

Please note that I am not an Erlang expert, I just want to make sure that your article is not dismissed because of the errors.

ilan

Yes, JRuby’s threads are always native, but you can specify that the native thread constructed gets pooled behind the scenes. This helps reduce the cost of spinning up a lot of threads. We have other plans to try to reduce the cost of spinning many small threads as well.

Ultimately, however, with or without the pool and non-trivial threaded application should see a lot better performance on JRuby, since the threads will *actually* run at the same time. Just don’t spin up a million tiny threads that add 1+1 and you’ll probably do fine.

If you want to model actual asynchronous behavior where the result depends on the order of execution, like with a client-server model, then you can use Ports in the style of the Oz language – or Actors in the style of erlang, which in this case are built on top of Ports!

But introducing state changes makes Ruby seem more like Ruby to begin with. It ‘undoes’ the determinism of dataflow variables. You would typically implement an identical Actor using a Ruby Queue.

I’ve updated the blog post to reflect your changes and your note about JRuby.

One thing to note is that this library makes JRuby shine over MRI due to its green threads + native thread pool implementation.

Another big advantage that I’d like to point out is that the specs in the library are using threads! Normally one mocks out threads for testing, but because this model is deterministic you can keep them in.

I believe the problem is your case statement is comparing a string with an integer. Type “value=gets” into IRB and then type the number 1. You’ll see that IRB tells you the result is the string “1\n”.

To fix this, convert the value to an integer before comparing it to 1, 2, or 3:
case value.to_i

Hope that helps!

True except when dealing with postgresql which supports DDL transactions

http://www.inwebwetrust.net/post/2008/08/19/redefine-the-run-method-of-test-unit-testcase

Anyway, this is what I did before finding Fernando’s approach:

For Unit Tests, add the setup method below in each test .rb file (you can also add a teardown method to log the end of the test, but having the start logged between each test was a good enough of delimiter for me). If you already have a setup method, of course just add the logger code line.

def setup
RAILS_DEFAULT_LOGGER.info “\n\nStarting #{@method_name}\n#{‘-’ * (9 + @method_name.length)}\n”
end

For Functional tests (because mine still use Test::Unit::TestCase), simply add the logger code line to the existing setup method.

Sorry for the previous posts and confusion. There is a better approach to keep this DRY, but until I figure that out, this is what I’ve done, it worked, so I thought I’d share — but I encourage you to learn the proper approach.

b

b

def setup
RAILS_DEFAULT_LOGGER.info “\n\nStarting #{@method_name}\n#{‘-’ * (9 + @method_name.length)}\n”
end

Or perhaps things have changed in a newer version of Rails. (Or an older one.)

The code above works in Rails 2.0.2. There’s a file called setup_and_teardown.rb that has these lines:

base.send :include, ActiveSupport::Callbacks
base.define_callbacks :setup, :teardown

define_callbacks creates a “setup” method and a “teardown” method as class methods. These methods are very much like the before_save, after_save, etc. methods, in that they take a parameter which is the name of a function to call before setup and after teardown. So my code that says “setup :log_test” tells the test framework to call the :log_test function before calling the “setup” instance method.

Perhaps things work differently in other versions of Rails.

I dropped the code into my Rails 2.0.2 app’s test_helper.rb and got this error trying to run a unit test:

./test/unit/../test_helper.rb:42: undefined method `setup’ for Test::Unit::TestCase:Class (NoMethodError)

Anyone else seeing this?

http://www.benmabey.com/2008/07/04/global-setup-in-rspec-or-how-to-add-logging-for-specs/

Happy July 4th!

i come to the same conclusion as you. Seems not to be working right now with NetBeans 6.1.

Perhaps somebody else figure out an soloution.

I keep watching the comments :)

What I’ve gotten working is running mongrel_rails from the command line.

When I run from within NetBeans I don’t get to see the response time on my pages. If you do figure out how to do that, it would be nice if you could post the solution as a comment here for others to see. From what I’ve seen so far of NetBeans’ Rails integration, it looks like it doesn’t currently have the flexibility to override how it runs the server.

thanks a lot Brian.

I just created the http_handlers folder and drop the benchmark_filter.rb into it, without success :)

But i suppose that my parameters: “-S lib/http_handlers/benchmark_filter.rb” are not at the right place for the NetBeans build-in Mongrel Server.

I googled this wiki entry: http://wiki.netbeans.org/FaqRailsMongrel and write ARGV+=%w(mongrel_rails start -S lib/http_handlers/benchmark_filter.rb) at the end of scripts/server File, but still not working.

Where should i put the benchmark_filter.rb?
(In the Rails App Lib Folder or in the Mongrel Lib Folder?)
Im using NetBeans 6.1.

Sorry, but im really new to the whole rails stuff.

I don’t know of a way to access the Rails ROOT_PATH from inside the BenchmarkFilter class because BenchmarkFilter is a Mongrel filter so it’s one level above Rails. It’s not running inside Rails so it doesn’t have access to the Rails environment.

The RailsHandler class, which is part of Mongrel, is what passes requests on to Rails. Maybe if you take a close look at that class you’ll find an answer to your question.

i tried to access the rails ROOT_PATH from inside the BenchmarkFilter class
but its returning the handler.rb’s path.

how should i get the rails ROOT_PATH.

HEMANTH

<%=
  case @results
  when nil then "No results"
  else @results.join ", "
  end
%>

The rest of us appreciate the WHOO HOOOs so we’ll know it’s time to grab our flame throwers.