On Mon, Sep 06, 2010 at 09:31:15PM -0700, Nathan Stults wrote: > > John, amazing work - I can't wait to apply this to my project tomorrow. > I love the two layers of extensibility - the service and the context, so > you can easily make (enhance) the DSL for your expressions or completely > swap everything out if you need something heavy duty. I'm on the fence > about returning nil when method missing is encountered. On the one hand, > trapping errors if a nil is possible would be a big pain, on the other, > if nils aren't generally possible, then an exception is much more > explicit. I think what you have is fine, or someday you could have a > flag like 'strict' or something as a static method of the service or > context if it ever became a problem for people. > > Whatever the case, there is now nothing left in ruote that will prevent > us from making it fit our solution like a glove, so I'm very > appreciative of your work.
Hello Nathan, I think I'm tempted to return nil, but I will give it more thinking. I know it's OK either way for you and I know you'll tell me if there anything wrong. > We'll be contributing a MongoDB storage service in the near future, so > we'll be sure to post a link when we do. What is your process when you > do a new storage back end? Do you have a common test suite you run to > verify the new storage mechanism, or do you write fresh tests for each > one? MongoDB ? Great ! There's so much buzz about it, I'd love someone to come up with a ruote storage for it. I have to say that I'd love it to be maintained (at least initially) by you guys. I have to watch my workload. That calls for a piece of documentation on what is expected from a storage and how to test it. Stay tuned for it. Many thanks, -- John Mettraux - http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
