mirror of
https://github.com/appy-one/acebase-client.git
synced 2026-05-24 22:01:18 -06:00
[GH-ISSUE #9] [discussion] Connect browser-based client to a local browser-based server? #7
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/acebase-client#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @willrogers007 on GitHub (Apr 19, 2021).
Original GitHub issue: https://github.com/appy-one/acebase-client/issues/9
Not meant so much as an issue to be solved, but more of a discussion topic / tentative-feature-request-if-it-makes-sense.
In the docs I've seen an example of a client using a local server as a cache, but I haven't seen an example of a client connecting to a local server as it would to a remote server.
The client creation options seem to expect a host/port, whereas I'd love to just pass a living server object reference in.
I imagine this could have some wild uses, especially if plugging it into something like WebRTC. Could enable a peer-to-peer database system, piggybacking on the acebase-server's ability to have authentication, access rules & schemas.
Anyways, color me intrigued; I'd be excited to explore in that direction.
@appy-one commented on GitHub (Apr 19, 2021):
Exactly what I've been thinking about the past weeks - using WebRTC for cross-browser synchronization. I'll be committing new IPC code for node clusters somewhere this week, which shares code for cross-browser-tab communication and leaves room for additional IPC implementations.