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.

Sign up for GitHub

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

Jump to bottom

Support multiple ATs each connecting to multiple browsers each with multiple tabs #10

Open
aleventhal opened this issue Apr 29, 2019 · 2 comments
Open

Support multiple ATs each connecting to multiple browsers each with multiple tabs #10

aleventhal opened this issue Apr 29, 2019 · 2 comments

Comments

@aleventhal
Copy link
Owner

Each browser will spawn a broker (native messaging host + tcp client).
Each AT needs to inform all current/future brokers that they are listening/interested in js2at messages.
@zork
@aleventhal
Copy link
Owner Author

ATs could add a file to a well-known directory location when connect to a port. The native messaging host could discover these files and read the port number from there.

@aleventhal aleventhal changed the title Support multiple ATs each connecting to multiple browsers Support multiple ATs each connecting to multiple browsers each with multiple tabs May 6, 2019
@aleventhal
Copy link
Owner Author

Seems like the multiple browsers (appId) and multiple tabs (docId) is addressed.
Need to support multiple ATs now.
While we do this, message broker not be launched if no AT connects to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aleventhal