Use Services module to provide REST interface?

Fixed title

I'm probably biased since I wrote the current REST implementation for ext 2, but after starting to have a go at modifying ext 2 to use the Services module I have the following impressions:

• I came across the "Retrieves are only allowed 1 path component, but unlimited params" limitation, this doesn't sit right with me at all (like I said, I may be biased ;)). I added this as a con to this issue summary; see the links for more info about why this might be a significant limitation.
• The Services module seems kind of complex (probably read: highly flexible and configurable), it would be nice to keep things simple with the current light-weight REST implementation.
• Another apparent limitation is not being able to specify an argument to a callback function that isn't dependent on run-time data (ie POST data, URL params, or path components), so while it may be highly configurable in some ways, we're still at the mercy of design decisions (limitations) that are largely out of our control unless we can get patches committed.

Of course this doesn't nullify the pros, but it does make me a lot less inclined to spend time on it (and probably won't bother with it unless someone else wants to write the code).

Added con about retrieves and paths versus params.