Yet, I get the feeling that the REST community would consider a solution that uses the REST architectural style but not HTTP and/or URI as “not RESTful”.
In general, I suspect that the community might balk. But I happen to believe that a resource-oriented communications protocol should be implementation independent. One should be able to implement a RESTful protocol in just about any messaging system.
You can do this in Ruby, and there is some argument whether it is a good thing to be able to do (in terms of readability, comprehensibility). You can override an existing method w/your own (I forget what the term is, right now, mainly because I never use it). Ruby on Rails takes full advantage of this.
Apparently, you can do the same thing in Flex, for the internal functions/capabilities of the MX Controls.
Void where prohibited, your mileage may vary, etc.