Add bLIP 55: Webhook Registration (LSPS5) #55
Conversation
tnull
force-pushed
the
2024-12-add-lsps5
branch
from
68e565d to
4b9484d
Compare
Hmm, good point in this case, as there is no implementation of this protocol as of today. We plan to add support to |
tnull
force-pushed
the
2024-12-add-lsps5
branch
from
4b9484d to
fb3434d
Compare
In typical mobile environments, a program that is not currently being focused on by the user will be suspended, with all its TCP connections dropped. This specification provides a way for a mobile client to register some specific webhook by which the LSP can signal a push notification to the application developer server, which will in turn convert the push notification to one that it itself signs and can send to the mobile OS developer server. The given protocol is based on LSPS0/bLIP 50 and has been previously stabilized by the LSP Spec group. As previously discussed on multiple occasions, the LSP Spec group is however moving to a bLIP-centric process, which is why we 'upstream' these previously-stabilized specifications here.
tnull
force-pushed
the
2024-12-add-lsps5
branch
from
fb3434d to
629294d
Compare
|
Rebased after #55 landed. |
|
Needs a rebase and this should be good to go? |
Ah, I though we'd wanted to wait with this until a reference implementation is available? |
Good point, if there is one that is being worked on then it's better to wait! |
Yes, there is work-in-progress, will give an update here once that has been merged! |
Based on #52.
In typical mobile environments, a program that is not currently being focused on by the user will be suspended, with all its TCP connections dropped.
This specification provides a way for a mobile client to register some specific webhook by which the LSP can signal a push notification to the application developer server, which will in turn convert the push notification to one that it itself signs and can send to the mobile OS developer server.
The given protocol is based on LSPS0/bLIP 50 and has been previously stabilized by the LSP Spec group.
As previously discussed on multiple occasions, the LSP Spec group is however moving to a bLIP-centric process, which is why we 'upstream' these previously-stabilized specifications here.
(cc the original author @ZmnSCPxj-jr)