1816135 - [meta] Design an asynchronous Places API

Status: RESOLVED DUPLICATE of bug 1816137

(Firefox :: Firefox View, task)

Description

[Jonathan Sudiaman [:jsudiaman]]

Upon further discussion with Marco, we've concluded that the best way forward for Firefox View is to design an asynchronous Places API and then connect synchronously that to the existing Places database. Our API will create a new connection to the database that is read only which should allow us to access history without the locking that the existing API causes.

The API will be designed with the future in mind (it won't be Firefox View specific). We'll consult with Marco on the implementation. It will only focus on our use cases though.

We do have older documentation, but Marco would prefer that we not start with that so we aren't biased toward a particular implementation. We can use https://searchfox.org/mozilla-central/source/toolkit/components/places/nsINavHistoryService.idl to get a general shape of the interfaces, but primarily it's going to involve someone playing with the API.

If you want to look at more API detail, we have some old documents here:

https://udn.realityripple.com/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsINavHistoryService

Based on the work week, our primary use case is going to be simple history querying for X number of entities and/or X number of days.

We are not going to enable searching or filtering initially, so the focus is very narrow.

Comment 1

[Jonathan Sudiaman [:jsudiaman]]

Having this meta bug doesn't really make sense as this only covers the API, and that work has been done in a single ticket. Subsequent work can go under Bug 1824826 if need be.