|
I did not suggest that there was a bug in the language. At first I
suggested that there might be a server problem . . . though as
I explained later, it was probably neither. This was almost certainly a scoping issue. While the server is running, the "application" gets the globals, and even when one controller "finishes" and "exits", your globals can be preserved. Your models may still be active and in memory, for example. But nowhere have I seen this documented, even in the best books or online. My main intent was to point out that regardless of whether it is intended behavior, using globals can cause problems if you are not careful and AWARE of how they work in Ruby and Rails. Their behavior is very poorly documented, where it is documented at all. Lonny Eachus ==========
|
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
