You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
The receiver currently generates tokens from individual payments, which the sender then attaches to individual HTTP requests for content. This means that the sender must make a full additional HTTP request to make the payment for each request they actually want to make.
A slightly more flexible way to set this up would be to generate a longer-lived token to identify a user. The user would send the same token with every request and could send a payment to cover one or more requests. The receiver would track an overall balance for the user and increase it when they send a new payment channel update it and decrease it for every request for content.
What do you think?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The receiver currently generates tokens from individual payments, which the sender then attaches to individual HTTP requests for content. This means that the sender must make a full additional HTTP request to make the payment for each request they actually want to make.
A slightly more flexible way to set this up would be to generate a longer-lived token to identify a user. The user would send the same token with every request and could send a payment to cover one or more requests. The receiver would track an overall balance for the user and increase it when they send a new payment channel update it and decrease it for every request for content.
What do you think?
The text was updated successfully, but these errors were encountered: