jsl-feedtosis 0.0.3.4 → 0.0.3.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.rdoc +12 -0
- data/feedtosis.gemspec +1 -1
- metadata +1 -1
data/README.rdoc
CHANGED
@@ -82,6 +82,18 @@ Generally, Feedtosis supports all systems supported by Moneta, and any one
|
|
82
82
|
of the supported systems can be given to the +moneta_klass+ parameter. Other
|
83
83
|
options following +backend+ are passed directly to Moneta for configuration.
|
84
84
|
|
85
|
+
== Feedtosis Fetch Results
|
86
|
+
|
87
|
+
The results of the Feedtosis Fetch will be a Feedtosis::Result object. You can call
|
88
|
+
"entries" and "new_entries" on this object. It also delegates methods to the curb object
|
89
|
+
so that you can inspect the HTTP response if necessary.
|
90
|
+
|
91
|
+
Note that if you find entries and new_entries to be nil it isn't necessarily indicative of an
|
92
|
+
error condition - it may just be that the resource wasn't downloaded since it wasn't modified
|
93
|
+
from the previous fetch! To determine if this was the case, call the method "response_code"
|
94
|
+
on the Results object. If the code is 304 (Not Modified), it means that it used HTTP conditional
|
95
|
+
GET to determine that the resource wasn't worth downloading as it contained no new information.
|
96
|
+
|
85
97
|
== Implementation
|
86
98
|
|
87
99
|
Feedtosis helps to identify new feed entries and to figure out when
|
data/feedtosis.gemspec
CHANGED