Re: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread drh
Doug Nebeker <[EMAIL PROTECTED]> wrote: > I've had a number of people express interest in the small HTTP > server. I'll work on commenting it a little better and then > put it out on a website in a day or two. > FWIW, the www.sqlite.org website is implemented using a webserver written as a

Re: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread Louis P. Santillan
Mozilla CVS builds of Rhino (JS in Java) and SpiderMonkey (JS in C) have E4X (ECMAScript for

[sqlite] strlen() and function args (PATCH)

2005-11-15 Thread Nathan Kurz
I've been looking at ways to make user defined functions run with less overhead, and found that OP_STRING and OP_STRING8 arguments are having strlen() called on them every time the function is invoked. Attached is a tiny patch that causes expr.c to pass the length of the argument as P1 and also

Re: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread Lindsay
[EMAIL PROTECTED] wrote: HTTP would be the logical choice, telnet is often firewalled. BTW, you can of course allready telnet into the server anyway. I will try doing something like this, but I have never implemented the server side of a HTML connection. Do you know where I can find a

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread Doug Nebeker
I've had a number of people express interest in the small HTTP server. I'll work on commenting it a little better and then put it out on a website in a day or two. -Original Message- From: Noel Frankinet [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 9:27 AM To:

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread roger
Thanks for the pointers and feedback. I have now grasped a very simple way to allow HTTP access via the same mechanisms. Back soon with the implementation :-)

Re: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread Noel Frankinet
Doug Nebeker wrote: I have a simple C++ HTTP server that I wrote (all in a single .cpp and .h file). Multi-threaded, has a session concept (via cookies), can parse POST and GET variables. It is a C++ class that you can derive from and then override the LoadFile method (which is where I

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread Doug Nebeker
I have a simple C++ HTTP server that I wrote (all in a single .cpp and .h file). Multi-threaded, has a session concept (via cookies), can parse POST and GET variables. It is a C++ class that you can derive from and then override the LoadFile method (which is where I typically put my

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread David Fletcher
> "r" == roger <[EMAIL PROTECTED]> writes: r> HTTP would be the logical choice, telnet is often firewalled. BTW, r> you can of course allready telnet into the server anyway. r> I will try doing something like this, but I have never implemented r> the server side of a HTML connection. Do

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread roger
> > HTTP is just a transport method. There is no reason why its payload > should not include your protocol if you want to tunnel through port 80. > You could embed it in TELNET also if you wanted to take advantage of > port 23. > JS HTTP would be the logical choice, telnet is often

Re: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread John Stanton
[EMAIL PROTECTED] wrote: I wrote it. I used XML in the end because it can map a complex data structure into a single document. In that case what you lose on the swings (XML) you gain on the roundabouts (TCP/IP), particularly if you use HTTP for transport. Just a thought. The TechFell

Re: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread John Stanton
[EMAIL PROTECTED] wrote: Original Message Subject: Re: [sqlite] uSQLiteServer Source code available From: John Stanton <[EMAIL PROTECTED]> Date: Mon, November 14, 2005 9:47 pm To: sqlite-users@sqlite.org [EMAIL PROTECTED] wrote: I like your concept and agree with your

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread roger
> > > I wrote it. I used XML in the end because it can map a complex data > structure into a single document. In that case what you lose on the > swings (XML) you gain on the roundabouts (TCP/IP), particularly if you > use HTTP for transport. Just a thought. The TechFell protocol as used

RE: [sqlite] uSQLiteServer Source code available

2005-11-15 Thread roger
> Original Message > Subject: Re: [sqlite] uSQLiteServer Source code available > From: John Stanton <[EMAIL PROTECTED]> > Date: Mon, November 14, 2005 9:47 pm > To: sqlite-users@sqlite.org > > [EMAIL PROTECTED] wrote: > >>I like your concept and agree with your design choices,