If I'm not mistaken, the thought is that if this relatively simpler service experiment goes well, then it will make sense to go ahead with pursuit of the bigger composite service (and probably a suite of services in due time).
Right, so we both agree we should start simplest—I just forgot the initial scope of this task:
Scope: the service takes an article name, and serves article content in a
text-only format (but including wikilinks and external links).
IOW: just learning about node, not necessarily building something we'll use in production.
On Tue, Feb 24, 2015 at 2:56 PM, Adam Baso abaso@wikimedia.org wrote:
I'd also like to add an "if-modified-since" support, so we can send GET
requests but only have data sent back over the wire if it's newer than Revision X or some etag has expired, etc.
Agreed.
Why aren't we doing something to solve a problem w/ the current apps? For example, aggregating image info and article info together into one response?
If I'm not mistaken, the thought is that if this relatively simpler service experiment goes well, then it will make sense to go ahead with pursuit of the bigger composite service (and probably a suite of services in due time).