[doc] end of parsing event + remote url about feedme.js HOT 9 CLOSED

Strange that the events are out of order. Just tried something similar to your example, and I get the item events before the end.

from feedme.js.

Thanks for a quick reply @fent!

Were you trying request(xxx) or something else? Could you please provide some example with remote file fetching and end event?

from feedme.js.

I tried http, and also request

var http = require('http');
var FeedMe = require('..');

var url = 'http://rss.nytimes.com/services/xml/rss/nyt/HomePage.xml';
var parser = new FeedMe(false);

parser.on('item', function() {
  console.log('item');
});

parser.on('end', function() {
  console.log('end');
});

http.get(url, function(res) {
  res.pipe(parser);
});

from feedme.js.

Ah. It seems that the problem may be in the execution times for item and end. The pipe is probably quickly firing several events one after another, and console.log('end') is called earlier since end is simpler to execute. But I may be wrong.

Would it be possible to have some callback after all other callbacks have finished executing?

from feedme.js.

If you look at the source for this, .emit() is called right away synchronously. It isn't deferred or queued up or anything.

from feedme.js.

Did you ever figure this out?

from feedme.js.

No. I could not find the way to emit some event strictly after all other callbacks have completed.

from feedme.js.

Can I see your exact code?

from feedme.js.

Never mind. I've already re-implemented what I wanted with another RSS-reading library.

from feedme.js.