Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify Waku Mailserver interface with req/resp #24

Closed
oskarth opened this issue Apr 13, 2020 · 4 comments
Closed

Simplify Waku Mailserver interface with req/resp #24

oskarth opened this issue Apr 13, 2020 · 4 comments
Assignees

Comments

@oskarth
Copy link
Contributor

oskarth commented Apr 13, 2020

Problem

Right now the Waku mailserver API is needlessly complex https://specs.vac.dev/specs/waku/mailserver.html and lack of more direct req/resp API makes working with them convoluted and error prone.

Solution

Investigate and propose what a KISS alternative would be with a more simple req/resp, as well what implications it would have for security etc.

Acceptance criteria

RFC / raw spec and PoC (e.g.).

@oskarth
Copy link
Contributor Author

oskarth commented Apr 13, 2020

IIRC you were looking into this before @decanus but not sure it was captured in an issue? Assigning you to capture this, if this isn't reasonable with commitment/time scale please adjust

Also cc @cammellos fyi if you know more about previous efforts here

@oskarth oskarth added this to the Vac April 2020 milestone Apr 13, 2020
@oskarth
Copy link
Contributor Author

oskarth commented Apr 23, 2020

See status-im/specs#54 (comment) for historical convo

@decanus
Copy link
Contributor

decanus commented Apr 27, 2020

Started research: vacp2p/rfc#116

@oskarth
Copy link
Contributor Author

oskarth commented Jul 1, 2020

@decanus can we finish this up to a point where we can hand it over to Stimbus with issues for improvements?

Then we can reformulate this in the context of Waku v2 track 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants