On 8-Sep-07, at 1:05 PM, Bart Silverstrim wrote:
> Anyway, I was saying that if the application worked, then it isn't
> against REAL's licensing to use the database that way?
I know of no licensing restrictions.
> Ah. The server portion I was referring to was an
> application/daemon/service that talked to the database and was the
> only
> part talking to the database.
>
> client app->(network connection)->server application<->database
>
> The server application handles requests from clients and arbitrates
> the
> data served, so no client is connecting to the database. The database
> talks to the server application as it queries for data.
This is effectively what REAL SQL Server does
>> Can you communicate between various apps and hack together a "multi
>> user" set up ?
>> Sure but you may have some issues.
>> For low volume stuff it will probably be OK.
>
> Hmm...
>
> So you're saying the scenario I'm posing would not violate RS's
> licensing, and if anything, only testing against real-world deployment
> would dictate problems with scaling. I'm guessing there's not
> anyplace
> that tested or benchmarked such things... :-/
Yes.
All I can point you at is the SQLite FAQ <http://sqlite.org/faq.html>
where they do talk about some related items (see items #5 and #6) and
the "Appropriate uses for SQLite" <http://sqlite.org/whentouse.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|