Skip to content
Extraits de code Groupes Projets
  1. mars 22, 2017
  2. mars 17, 2017
  3. fév. 22, 2017
  4. fév. 16, 2017
  5. fév. 05, 2017
  6. jan. 30, 2017
  7. jan. 29, 2017
  8. jan. 27, 2017
  9. jan. 26, 2017
  10. jan. 23, 2017
  11. jan. 21, 2017
  12. jan. 20, 2017
  13. jan. 19, 2017
  14. jan. 18, 2017
  15. jan. 12, 2017
  16. jan. 11, 2017
  17. déc. 21, 2016
  18. déc. 13, 2016
  19. nov. 29, 2016
  20. nov. 24, 2016
  21. nov. 22, 2016
  22. nov. 15, 2016
  23. nov. 12, 2016
  24. nov. 09, 2016
  25. nov. 07, 2016
  26. nov. 06, 2016
  27. nov. 04, 2016
  28. nov. 02, 2016
  29. oct. 14, 2016
  30. oct. 07, 2016
  31. oct. 02, 2016
  32. sept. 24, 2016
  33. sept. 20, 2016
    • Eugen Rochko's avatar
      Fix #24 - Thread resolving for remote statuses · 4bec6138
      Eugen Rochko a rédigé
      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.
      4bec6138
  34. sept. 18, 2016
  35. sept. 12, 2016
Chargement en cours