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
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
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
John Stanton wrote:
> Perhaps a thread per open database sync'd on an event and driven by a
> queue would give you contention-free operation and avoid the need to
> ever have the DB locked.
>
> A thread would post its request to the queue then wait on an event
> signifying completion.
That's
I know the restriction of passing open databases across threads. What I'm
wondering is whether that's really a process/thread issue, or a concern over
making sure two or more threads don't muck with a single database at the
same time.
Basically, I'm exploring how I might implement database
Those suggestions are great. For something like log analysis, there's no
problem either reading in log file tails ever so often or queuing up a
single thread to give more real-time access. I think I'm leaning towards a
more real-time view, but I might take the tail option if it codes easier.
On
I've been exploring SQLite for a number of applications, but one I'd like to
embark on soon is using SQLite to record Web site log file data, so I can
perform SQL-based analysis on my logs, rather than using some thing like
Analog.
Unfortunately, each Web access on the server is likely to be in
I've started writing my first wrappers for SQLite compiled inside the
Frontier Kernel and I've run into a snag. I have one verb that calls
sqlite3_open. It returns successfully and sets the db properly. If, in that
same routine, I call sqlite3_close, it works successfully.
But, if I return from
:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 10:07 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Writing wrappers?
David Gewirtz said:
>
> I've just started to explore SQLite and I've noticed a whole pile of
> wrappers for various environments. The environment I'm using
I've just started to explore SQLite and I've noticed a whole pile of
wrappers for various environments. The environment I'm using (the open
source Frontier Kernel) doesn't have any wrappers, so I'd like to write one.
Can someone post some pointers to resources on how to get started writing
10 matches
Mail list logo