Another library option would be JLog
https://labs.omniti.com/trac/jlog
enjoy,
-jeremy
On Tue, May 11, 2010 at 02:44:18PM -0500, Manuj Bhatia wrote:
> I need to exchange messages across processes, not threads. And one of the
> reasons that I am inclined towards SQLite is that I do not want a
I need to exchange messages across processes, not threads. And one of the
reasons that I am inclined towards SQLite is that I do not want a separate
Queue-manager process.
I'll just write wrapper APIs around SQLite and embed them into each
application, so I have a manager-less implementation.
I fo
Hm... You can use the dedicated thread in your application for SQLite
in-memory database. Why you want to build external application for
this? And SQL for you task is not needed I think - you can use the
simple hash table or any other simple structure. If you have same
additional needs or ideas - s
qlite-users-boun...@sqlite.org on behalf of Manuj Bhatia
Sent: Tue 5/11/2010 11:15 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] SQLite Database in Shared Memory
I am developing this solution for an AIX machine. I am not sure if it does
any such optimization for the temp
I am developing this solution for an AIX machine. I am not sure if it does
any such optimization for the temp file system.
As someone recommended, I can probably implement a VFS for Shared-memory,
but that seems to be too much work :)
I am inclining towards a file-based DB with syncs turned off. I
I am sorry... when I said IPC-based I really meant an IPC-Queue-based (the
standard msgget()/mq_open() stuff).
I have nothing against IPC :). It's just that an IPC-queue solution will not
satisfy all my requirements.
I will definitely be using IPC semaphore/mutex facility to avoid having to
poll th
Manuj Bhatia wrote:
> I do not have a requirement of persistence in my current design, but I
> expect that we might extend this shared-queue solution to more areas of
> the server and will require some sort of persistence then.
> That is one of the main reasons I do not want to use IPC queues
> In short, using a SQLite-backed queue solution gives me a lot of options
> that a simple IPC based (and, for that matter, even a professional Messaging
> Product) does not give.
Also SQLite-backed solution gives you a big restriction that IPC
doesn't: you have to poll the queue instead of pushin
Michael D. Black
Senior Scientist
Northrop Grumman Mission Systems
From: sqlite-users-boun...@sqlite.org on behalf of Manuj Bhatia
Sent: Mon 5/10/2010 2:59 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] SQLite Database in Shared Memory
Pavel,
I do not have a requirement of persistence in my current design, but I
expect that we might extend this shared-queue solution to more areas of the
server and will require some sort of persistence then.
That is one of the main reasons I do not want to use IPC queues (there are
other reasons
On 10 May 2010, at 4:47pm, Alexey Pechnikov wrote:
> TCP-socket listening daemon + SQLite in-memory database may be helpful.
Yes. You can make one process, which handles all your SQLite transactions, and
receives its orders from other processes via inter-process calls or TCP/IP.
I've seen a
On Mon, May 10, 2010 at 11:15:59AM -0400, Pavel Ivanov scratched on the wall:
> > Any ideas about how to implement a DB in shared memory?
>
> It's impossible with current SQLite code base. Even if you try to
> implement your own database cache and will allocate it in some shared
> memory it won't
TCP-socket listening daemon + SQLite in-memory database may be helpful.
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> Any ideas about how to implement a DB in shared memory?
It's impossible with current SQLite code base. Even if you try to
implement your own database cache and will allocate it in some shared
memory it won't work because along with cache pages SQLite also stores
some internal information which s
Hi,
I am trying to implement a shared queue (to asynchronously exchange messages
between processes) using SQLite.
Since I do not need my queues to be persistent (at least for now), I do not
want to use disk based SQLite database (for better performance).
I see there is an option to create purely
15 matches
Mail list logo
