David Gewirtz wrote:
John Stanton wrote:
I don't understand how you apply Frontier. To build a multi-threaded web
server
hosting Sqlite looks like a project to replace Frontier, which already has
embedded Sqlite.
Ah, ok, let's back up. I and some other developers finished adding SQLite
John Stanton wrote:
>
> I don't understand how you apply Frontier. To build a multi-threaded web
server
> hosting Sqlite looks like a project to replace Frontier, which already has
embedded Sqlite.
Ah, ok, let's back up. I and some other developers finished adding SQLite
into Frontier last mont
David Gewirtz wrote:
John Stanton wrote:
What language are you using? Certain language environments would make
implementing the server clumsy.
I'm using an environment called the Frontier Kernel
(http://www.frontierkernel.org), which is the open source version of the
original UserLand Front
John Stanton wrote:
> What language are you using? Certain language environments would make
implementing the server clumsy.
I'm using an environment called the Frontier Kernel
(http://www.frontierkernel.org), which is the open source version of the
original UserLand Frontier. As obscure as that
The traditional CGI approach is to open and close the database for each
transaction. If you build your own threaded server to avoid that it
does not make sense to continue the open and close situation.
Opening and closing the DB is not an enormous overhead, but is ugly if
your clients are usi
"David Gewirtz" <[EMAIL PROTECTED]> wrote:
>
> Basically, is it bad if I decide to open and close the same database a LOT?
It isn't the best choice if performance is your goal. Every time
you open the database, it has to read and parse the entire schema.
SQLite does that pretty quickly as databa
On Thu, 9 Nov 2006, David Gewirtz wrote:
Basically, is it bad if I decide to open and close the same database a
LOT? For example, rather than opening a database when the server boots and
keeping it open for the duration, is it bad if I open it for every query
and close it right away? I'd set som
In my ongoing attempt to find the best approach for integrating SQLite into
a threaded Web-serving environment, I came upon a truly crude kludge, and I
wanted to know if it's bad from an SQLite architectural standpoint. I know
it's bad morally and ethically.
Basically, is it bad if I decide to op
8 matches
Mail list logo
