<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Active Record on Minko Gechev&#39;s blog</title>
		<link>https://blog.mgechev.com/tags/active-record/</link>
		<description>Recent content in Active Record on Minko Gechev&#39;s blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 05 Feb 2014 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.mgechev.com/tags/active-record/feed.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The magic of $resource (or simply a client-side Active Record)</title>
				<link>https://blog.mgechev.com/2014/02/05/angularjs-resource-active-record-http/</link>
				<pubDate>Wed, 05 Feb 2014 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2014/02/05/angularjs-resource-active-record-http/</guid>
				<description>&lt;p&gt;At first sight AngularJS seems like a magical framework, which does some weird but awesome things like dependency injection, data binding only by setting a single property to the magical object named $scope and many other things.&lt;/p&gt;&#xA;&lt;p&gt;If you look at the source code of Angular you’ll see a lot of smart and simple solutions for these magical problems. In this blog post I’ll describe the magic which stays behind &lt;code&gt;$resource&lt;/code&gt;. I decided to write this blog post because of my recent experience in StackOverflow. One of the most misunderstood components of AngularJS was exactly the &lt;code&gt;$resource&lt;/code&gt; service. &lt;code&gt;$resource&lt;/code&gt; is two levels of abstraction above the XMLHttpRequest object (ok, may be three if we count &lt;code&gt;$httpBackend&lt;/code&gt;). I’ve illustrated the usage of &lt;code&gt;$resource&lt;/code&gt; through example which can be found at &lt;a href=&#34;https://github.com/mgechev/angularjs-resource&#34;&gt;GitHub&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
