8 Commits (938cd2875b14db3655a6c9f82f672f4baf7720a3)

Author	SHA1	Message	Date
Eugen Rochko	f722bd2387	Separate background jobs into different queues. ATTENTION: new queue "pull" ... must be added to the Sidekiq invokation in your systemd file The pull queue will handle link crawling, thread resolving, and OStatus processing. Such tasks are more likely to hang for a longer time (due to network requests) so it is more sensible to not make the "in-house" tasks wait for them.	8 years ago
Eugen Rochko	6c28886317	Improve background jobs params and error handling	8 years ago
Eugen Rochko	668013265c	Restoring old async behaviour of thread resolving as it proved to be more robust	8 years ago
Eugen Rochko	f90133d2ad	Thread resolving no longer needs to be separate from ProcessFeedService, ... since that is only ever called in the background	8 years ago
Eugen Rochko	2d2c81765b	Adding embedded PuSH server	8 years ago
Eugen Rochko	fdc17bea58	Fix rubocop issues, introduce usage of frozen literal to improve performance	8 years ago
Eugen Rochko	927333f4f8	Improve code style	8 years ago
Eugen Rochko	4bec613897	Fix #24 - Thread resolving for remote statuses ... This is a big one, so let me enumerate: Accounts as well as stream entry pages now contain Link headers that reference the Atom feed and Webfinger URL for the former and Atom entry for the latter. So you only need to HEAD those resources to get that information, no need to download and parse HTML <link>s. ProcessFeedService will now queue ThreadResolveWorker for each remote status that it cannot find otherwise. Furthermore, entries are now processed in reverse order (from bottom to top) in case a newer entry references a chronologically previous one. ThreadResolveWorker uses FetchRemoteStatusService to obtain a status and attach the child status it was queued for to it. FetchRemoteStatusService looks up the URL, first with a HEAD, tests if it's an Atom feed, in which case it processes it directly. Next for Link headers to the Atom feed, in which case that is fetched and processed. Lastly if it's HTML, it is checked for <link>s to the Atom feed, and if such is found, that is fetched and processed. The account for the status is derived from author/name attribute in the XML and the hostname in the URL (domain). FollowRemoteAccountService and ProcessFeedService are used. This means that potentially threads are resolved recursively until a dead-end is encountered, however it is performed asynchronously over background jobs, so it should be ok.	8 years ago