> hey, this might be a dumb Q, but if you want to save state between RPC
> method calls, do you have to do anything special? variables i declare
> outside the return scope are available in the closure, but i can't set
> them. does socketstream reinstantiate the return object each call to rpc or
> am i making a silly javascript faux pas?  

> Here's an example-- this logs Object when it should log Timer:

> https://github.com/polidore/ss-angular/blob/rpc/example/server/rpc/ex...

> Just to prove I'm not going crazy: this is valid JS.

> var a = {}
> undefined
> var c = { on: function() { a = 9 }, off: function() {console.log(a); a =
> 10}}
> undefined
> c.on()
> undefined
> a
> 9
> c.off()
> 9
> undefined
> a
> 10

> Yes you're right, we need to run the exports.action closure each time to
> allow the middleware to execute.

> Therefore if you really don't want to use a db, just put your variable
> outside of the closure:

>   var intervalId = {};

> exports.actions = function(req,res,ss) {
>   var crypto = require('crypto');

>   return {
>     on: function() {
>       etc etc...

> Owen

> Thanks. That makes sense.

> On Sun, Jul 8, 2012 at 9:50 AM, Owen B <socketstreami...@gmail.com> wrote:

>> Hey Benjamin

>> Yes you're right, we need to run the exports.action closure each time to
>> allow the middleware to execute.

>> Therefore if you really don't want to use a db, just put your variable
>> outside of the closure:

>>   var intervalId = {};

>> exports.actions = function(req,res,ss) {
>>   var crypto = require('crypto');

>>   return {
>>     on: function() {
>>       etc etc...

>> Owen

> So really anything expensive (such as nodejs require()) should probably be
> done outside the closure if possible for performance reasons, right?