tursodatabase / tursodatabase/libsql
Unix sockets for embedded libsql
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
I was thinking about how libsql can be embedded into the same node the an application is running on and wondering if unix sockets were in use for client->libsql comms in this case, if not, is that of interest to roadmap/team/community?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by checking how embedded libsql handles client-to-libsql communication and whether Unix sockets are already used; a complete outcome would define whether this belongs on the roadmap and what implementation scope it requires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100