Skip to content

question: could you explain the need for the cbor-x in the client code? #2

Open
@ckot

Description

Hi, perhaps I'm misunderstanding something, I don't understand why the client code is making use of cbor-x rather than simply using something to the effect of:

const repo = new Repo({
  network: [new BrowserWebSocketClientAdapter('<my wss server url')],
  storage: new IndexedDBStorageAdapter(),
})

Basically I'm wanting to self-host my own web-socket server and automerge repo (with file system storage). I thought I understood the server-side code to a nice simple example of how to do this, but after seeing the client-side code, I'm unsure if a "sync server" is doing something other than what I want.

Any explanation, no matter how brief, would be appreciated.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions