Yipes, I'm behind on my e-mail!While I agree with most of the replies to this thread earlier regarding the overhead, there are times when calling a REST web service is handy (although not in the context you're talking about)... So I just wanted to mention that I uploaded a thin wrapper that lets you create a Catalyst model out of a REST service:
http://search.cpan.org/dist/WebService-CRUST/lib/Catalyst/Model/ WebService/CRUST.pm
I'd be interested in any feedback anyone has.(and I just noticed the error in the docs where $c->stash{result} should be $c->stash->{result}, etc)
On May 24, 2007, at 11:34 AM, John Goulah wrote:
What are peoples thoughts on using REST not only as a web service, but also within the application itself as another layer of abstraction? I would assume in this way all the DB related calls would go through the REST layer, and this way they can be invoked as services or locally through the app. Is this too much overhead since the model itself is a layer?What are the best ways to deal with this from a security aspect (such as making sure people dont call some DELETE action on senstive data)? Is this handled with authorization or some other such way? I wouldn't want an "authorized" user to delete content they aren't authorized to delete of course.What are some of the patterns people are using to implement this? Any other thoughts?Thanks! John
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
