Thanks Sander.
Until now I have always just written my own services using $http and never
had a problem. In a way, though, I kinda get the impression that $resource
is the "right" way to do this kind of thing. But if I find myself tending
to do things like,
$resource('/path/to/res').get({},function(){//some success
handling},function{//some error handling})
should I just be using $http anyway?
Either way it bugs me that I can't get $resource to work, so I'll try what
you suggested first. But it would be great if you could convince me that
using custom services with $http instead of $resource isn't considered "bad
practice". I actually never saw much benefit of $resource over $http other
than its syntax being a bit more concise. I know there are probably
countless posts on "$http vs $resource", but maybe you can spell it out for
me one more time?
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
