Alexis, did you look at this part of the documentation (URL below) on deployment?
Also, if you need multiple connections at the same time, then you need to decide:
- If you only need one deployment (like a web service you offer yourself to your customers), then you should get a commercial copy of Valentina Server
- If you need to deploy unlimited copies to your customers (each customer gets their own server), then you need VDN
1) Is this application going to be used by just one person on his/her own computer without any other person connecting to it.
2) Is your application going to be installed in a client/server methodology. i.e.: Separate installs of a main server and individual client installs on different computers where each client connects to the server on a network (locally or remote).
3) Is your application a single server type app that is installed centrally on a web server and all your clients will connect through a web browser.
Each one of these variations have different requirements for ADK and VServer (commercial and VDN).
ADK vs VDN:
If you're designing a standalone app, such as a maybe a personal finance manager, that only one person will be using on his/her computer - then you need to design your app using the ADK (DB and Reports). This ADK can provide your app with local databases and reports. Depending on which OS platform you are writing your app for, you will need your IDE (or you can do manually) copy the vcomponents folder to the target computer (the link provides default locations for the various OSes) or in your app's bundle when installing.
If you are designing the same app to be used in a team environment, let's say a company wants every one on the staff to manage company finances using a single app (client apps connecting to a central database server) then you will need two (usually) separate apps - a client app and a server app. For your server app, you will need to install the embedded VServer VDN if this is an app that you develop and sell commercially. If it is for you (or your company only) then the VServer licensing will be ok. (This is how I read the licensing agreement - maybe Lynn can chime in and correct me if I am wrong.)
If your application is a web app where clients use a web browser to connect to a single DB server that you provide to customers for local install on their own web server, then the VDN VServer licensing would still apply (again, as far as I understand the licensing FAQ) because a standard VServer license is licensed to you only and not for distribution.
By stating you need 5 max, then this is the licensing you purchase thru Valentina for your VServer product. Generally you will need a VDN server license that includes 5 concurrent connections on whatever type you need (SQLite, REST, or VDB). This allows 5 separate clients to connect at the same time.
On a related note: Although VSQLite server is a venerable product, I highly recommend you use Valentina DB for your database needs instead of SQLite. It is much more scalable and the performance pounds SQLite into the dirt. All developers have a preference, and when the platform dictates I still use SQLite (on iOS for instance), but even then I still use VDB on the backend in a client/server app scenario.
I have done this same set up before - your server/client app will use the VDN embedded server and then your clients can connect to it. If your client apps are only connecting via Valentina.initClient() then they do not need a separate ADK license.
Unless you're using persistent connections, I wouldn't get so wrapped up in number of connections. I have a client that only has a 5 connection license and they have 18 people in the office.
Structure your code to open the connection, do your queries, updates, etc, and then close the connection. This happens very quickly if on a local network. Another advantage to VServer is if a client attempts to connect and all connections are in use, it will wait (your timeout parameter) and retry. I let the client decide if he/she needs concurrent/persistent connections and the $ will adjust accordingly.
I am not sure what language you're writing your app with, but I just write a small connection routine and show a dialog window that says wait, or connecting, etc... while the app attempts to connect and do its thing.
Bottom line is: Is this an app you are writing for your own use? Or is it something you are selling commercially? Huge difference in licensing (and cost).
I have a standard VServer license for all the stuff we do here in the office (our own apps, etc...) and I have a VDN embedded license for everything we sell/license to others.