🦆
ws4sqlite
v0.16
v0.16
  • 🌱Introduction & Credits
  • 🥇Features
    • 🚄Performances
  • 🏫Tutorial
  • 🔦Cheat Sheet
  • 🏗️Building & Testing
  • 🛡️Security
  • 📖Documentation
    • 🔧Installation
      • 🐳Docker
    • 🏃Running
    • 📃Configuration File
    • 🔓Authentication
    • 📦Stored Statements
    • ❓Requests
    • ❗Responses
    • ❌Errors
    • 🔨Scheduled Tasks
    • 🌐Embedded Web Server
  • 💡Client Libraries
  • 🎓Advanced Topics
  • 🪐Integrations
    • ⚙️Reverse Proxy
  • ⚖️License
  • 👷GitHub Repository
  • 🚁Support on Discord
Powered by GitBook
On this page
Edit on GitHub

Client Libraries

PreviousEmbedded Web ServerNextAdvanced Topics

Last updated 1 year ago

Client libraries are provided, with bindings to contact ws4sqlite from your code.

The reasons are several:

  • You don't have to deal directly with JSON, which can be cumbersome in some languages;

  • You have the convenience of type safety and compile-time checks, in languages that support them;

  • The library performs checks for the requests being well formed, preventing errors;

  • It maps the errors to the language platform's idiomatic facilities.

With clients, ws4qlite acts as a remote protocol for SQLite.

Platforms

We provide libraries for:

  • Java/JDK:

  • Go(lang):

  • ...more to follow

💡
https://github.com/proofrock/ws4sqlite-client-jvm
https://github.com/proofrock/ws4sqlite-client-go