Closed
Bug 1631768
Opened 4 years ago
Closed 4 years ago
Re-consider glean-sdk / FOG API split
Categories
(Toolkit :: Telemetry, enhancement, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
People
(Reporter: janerik, Assigned: Dexter)
References
Details
(Whiteboard: [telemetry:fog:m6])
Right now we opt for implementing the proper Rust API directly inside m-c as part of the FOG API.
It interacts with glean-core, the somewhat-internal layer of the Glean SDK.
In the future a potential glean-sdk should be usable by any Rust consumer, with m-c wrapping that instead of glean-core, thus guaranteeing we only use a proper specified and consistent API across all projects.
The FOG API can be the test bed to flesh out the API details first.
|
Reporter | |
Updated•4 years ago
|
Summary: Re-consider glean-skd / FOG API split → Re-consider glean-sdk / FOG API split
|
||
Updated•4 years ago
|
Priority: -- → P3
|
|
||
Updated•4 years ago
|
Severity: -- → N/A
|
Assignee | |
Comment 1•4 years ago
|
||
For some reason I forgot to take this bug. In any case, here's the proposal.
What do you both think?
Assignee: nobody → alessio.placitelli
Flags: needinfo?(jrediger)
Flags: needinfo?(chutten)
Priority: P3 → P1
|
|
||
Comment 2•4 years ago
|
||
Looks sensible. I have comments that I have left in the doc.
Flags: needinfo?(chutten)
|
|
Reporter | |
Comment 3•4 years ago
|
||
Questions in the doc. Overall a sensible approach, some details are not super clear to me yet.
Flags: needinfo?(jrediger)
|
|
||
Updated•4 years ago
|
Whiteboard: [telemetry:fog:m?] → [telemetry:fog:m6]
You need to log in
before you can comment on or make changes to this bug.
Description
•