-
Notifications
You must be signed in to change notification settings - Fork 283
Evaluate integration of the web relay #1851
Comments
Update:
(3) is really important since while the relay code will make our offline messaging system more robust generally speaking, it might resolve the issue where offline chat and order messages being published to the network are being interrupted when the user hard closes the app. Testing
|
I think this POC could be merged for general use with the following improvements (for considering during our planning call):
|
@hoffmabc we got distracted with a bunch of work obviously, but this would still be helpful to put some data behind the theory. |
I've updated the description with the requirements as discussed in our meeting today (with a few amendments). Please ACK this comment or respond with recommended changes once you've had a chance to review. |
Overview
Some time ago we put together https://github.com/OpenBazaar/webrelay, which is a server designed to:
This is not to be confused with the IPFS relay that facilitates two online nodes forming a connection for direct interactions. The purpose of the web relay is to make publishing offline messages more reliable, and the detection of offline messages more immediate.
This infrastructure is presently used by Zokos to great effect (kudos @rodkeys). Presently, we've started experimenting how this would work in Haven, and since things are getting more serious, we should capture the work in this issue.
Hypothesis
Our expected utility for this work:
Phase 1: Feasibility study
We want to evaluate whether our hypothesis :
The manner of this implementation will suit quick testing and not production-level code. If our testing demonstates an improvement in offline message publishing and delivery, then we'll move onto phase 2.
Phase 2: Production integration
After looking at the code we prepared in the branch, we will:
A parallel discussion needs to happen with the infrastructure team, who will be responsible for maintaining the web relay.
Other considerations
Requirements discussed in planning
Client
Server
The text was updated successfully, but these errors were encountered: