Re: [AOLSERVER] Generating .pdf Files on the Fly
We use HTMLdoc via command line interface; converts HTML -> PDF or PS http://www.easysw.com/htmldoc/ Best regards -gustaf neumann - Original Message - From: "Nathan Folkman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 14, 2004 11:32 PM Subject: [AOLSERVER] Generating .pdf Files on the Fly > Is anyone doing this? More importantly, is anyone doing this via Tcl? > Any pointers would be appreciated. Thanks! > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Fun: Fortune module
Can be used for fun :-)) I uploaded fortune module, similar to Unix fortune command, uses same files and returns random epigrams. http://www.crystallballinc.com/vlad/software/ -- Vlad Seryakov 703 488-2173 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Generating .pdf Files on the Fly
I've used Apache FOP. It works pretty well but it's in Java. You don't really need to know Java to use it since it relies on XML and stylesheets On Jul 14, 2004, at 4:32 PM, Nathan Folkman wrote: Is anyone doing this? More importantly, is anyone doing this via Tcl? Any pointers would be appreciated. Thanks! -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Generating .pdf Files on the Fly
Good pointers! Thanks everyone! Vlad Seryakov wrote on 7/14/04, 5:39 PM: > We are doing it using AwareReports http://www.awaresw.com, but we bought > their product, it is comercial. > We are calling external program now, but they have C++ API and we > started writing aolserver module for it, just never finished. > > It is very fast and supports Excel, PDF, PS formats. > > Nathan Folkman wrote: > > Is anyone doing this? More importantly, is anyone doing this via Tcl? > > Any pointers would be appreciated. Thanks! > > > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > > -- > Vlad Seryakov > 703 488-2173 office > [EMAIL PROTECTED] > http://www.crystalballinc.com/vlad/ > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Generating .pdf Files on the Fly
We are doing it using AwareReports http://www.awaresw.com, but we bought their product, it is comercial. We are calling external program now, but they have C++ API and we started writing aolserver module for it, just never finished. It is very fast and supports Excel, PDF, PS formats. Nathan Folkman wrote: Is anyone doing this? More importantly, is anyone doing this via Tcl? Any pointers would be appreciated. Thanks! -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- Vlad Seryakov 703 488-2173 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Generating .pdf Files on the Fly
> Is anyone doing this? More importantly, is anyone doing this > via Tcl? Any pointers would be appreciated. Thanks! There is a pdflib that generates this stuff and has Tcl bindings, but IIRC it didn't have the friendliest license terms. See http://wiki.tcl.tk/pdf for more info. Jeff -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Generating .pdf Files on the Fly
Is anyone doing this? More importantly, is anyone doing this via Tcl? Any pointers would be appreciated. Thanks! -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
A suggestion: the SQLite DB driver could keep a serial number that is incremented whenever the DB is modified by the driver. The driver could then re-open the DB if the file handle it gets from gethandle is stale. It wouldn't work in the case of another process outside the web server modifying the database, but maybe that could be done with a periodic check of the DB file's timestamp. > > On Wed, Jul 14, 2004 at 02:51:44PM -0400, Dossy wrote: > > > "SQLite version 3.0 is made possible in part by AOL developers > > supporting and embracing great Open-Source Software." > > > > I wonder what this is all about. Anyone know? > > No idea. Sounds interesting, though. :) > > > And, from the FAQ at http://www.sqlite.org/faq.html: > > > | Note that if two or more threads have the same database open and > > | one thread creates a new table or index, the other threads might > > | not be able to see the new table right away. You might have to get > > | the other threads to close and reopen their connection to the > > | database before they will be able to see the new table. > > > Pargraph #3 bothers me. If this is the case (changes in one thread not > > picked up by the other threads unless they close/reopen the DB), that's > > a pretty tough limitation. > > Dossy, like it or not, that's because by design, the ONLY operating > system services SQLite uses for locking are a file locks on the > database file. (More or less; if I remember right, it's actually a > bit more complicated than that, but that's the general idea.) > > For AOLserver use, you basically have two simple options: > > 1. Open and close the SQLite db file for EVERY transaction. This is > the normal way to use SQLite, and is definitely what you have to do if > other processes might also be accessing the same database. > > 2. Keep the database open, and serialize all SQLite operations through > a single thread. > > I would prefer to see an optional single-process many-threads MVCC > concurrency model for SQLite, and several variants of that have been > discussed rather extensively on the SQLite list. But so far no one > has implemented it, and it's rather outside Dr. Hipp's primary design > goals for SQLite. > > SQLite 3.0 introdues some new stuff to improve concurrency, but it > doesn't go nearly as far as full-blown MVCC. That said, the SQLite > wiki has numbers suggesting that the concurrency achievable even with > the older 2.8.x SQLite is probably adequate for many small to medium > websites: > > http://www.sqlite.org/cvstrac/wiki?p=WhenToUseSqlite > > My personal SWAG, is that if you can run your website ok on MySQL, you > can probably run it just fine on SQLite too. > > -- > Andrew Piskorski <[EMAIL PROTECTED]> > http://www.piskorski.com/ > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with > the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field > of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On Wed, Jul 14, 2004 at 02:51:44PM -0400, Dossy wrote: > "SQLite version 3.0 is made possible in part by AOL developers > supporting and embracing great Open-Source Software." > > I wonder what this is all about. Anyone know? No idea. Sounds interesting, though. :) > And, from the FAQ at http://www.sqlite.org/faq.html: > | Note that if two or more threads have the same database open and > | one thread creates a new table or index, the other threads might > | not be able to see the new table right away. You might have to get > | the other threads to close and reopen their connection to the > | database before they will be able to see the new table. > Pargraph #3 bothers me. If this is the case (changes in one thread not > picked up by the other threads unless they close/reopen the DB), that's > a pretty tough limitation. Dossy, like it or not, that's because by design, the ONLY operating system services SQLite uses for locking are a file locks on the database file. (More or less; if I remember right, it's actually a bit more complicated than that, but that's the general idea.) For AOLserver use, you basically have two simple options: 1. Open and close the SQLite db file for EVERY transaction. This is the normal way to use SQLite, and is definitely what you have to do if other processes might also be accessing the same database. 2. Keep the database open, and serialize all SQLite operations through a single thread. I would prefer to see an optional single-process many-threads MVCC concurrency model for SQLite, and several variants of that have been discussed rather extensively on the SQLite list. But so far no one has implemented it, and it's rather outside Dr. Hipp's primary design goals for SQLite. SQLite 3.0 introdues some new stuff to improve concurrency, but it doesn't go nearly as far as full-blown MVCC. That said, the SQLite wiki has numbers suggesting that the concurrency achievable even with the older 2.8.x SQLite is probably adequate for many small to medium websites: http://www.sqlite.org/cvstrac/wiki?p=WhenToUseSqlite My personal SWAG, is that if you can run your website ok on MySQL, you can probably run it just fine on SQLite too. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
Dossy wrote: | Note that if two or more threads have the same database open and | one thread creates a new table or index, the other threads might | not be able to see the new table right away. You might have to get | the other threads to close and reopen their connection to the | database before they will be able to see the new table. Pargraph #3 bothers me. If this is the case (changes in one thread not picked up by the other threads unless they close/reopen the DB), that's a pretty tough limitation. This limitation is not related to threads, but SQLite itself. From Q7: If two or more processes have the same database open and one process creates a new table or index, the other processes might not be able to see the new table right away. You might have to get the other processes to close and reopen their connection to the database before they will be able to see the new table. The easiest way would be to create a global counter and increment it when database schema has changed (this could be triggered by hand by [ns_sqlite reopen]). However this would include mutex locking on every query, which would slow things down. SQLite deifnitely has its place, especially as an even lighter-weight alternative to MySQL, but I'd still urge folks to look at MetaKit, which has been around since 1996, compared to SQLite since 2000. My guess is that SQLite is much easier to use than MetaKit. I've tried MK, but never got to like it, although I find subviews really interesting. -- WK -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
Dossy said: > Also, for folks who want transaction-safe database but don't want to go > so far as to learn or use SQL, I'd like to remind folks about MetaKit: What I like about SQLite is that it is actualy SQL and thus it would be easy to write an app that runs fine for a small site on SQLite and larger sites would simply run it on a "real" RDBMS. I can even see a model where you download an installer that has AOLserver as "embedded" HTTP server and SQLite as DB. Even the CIO could install it on his workstation and evaluate the product! Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On Wed, Jul 14, 2004 at 07:58:18PM +0200, Wojciech Kocjan wrote: > Ok, I'll clean things up, license it as BSD. Does anyone know if sqlite > 3.0.2 is stable or development release? Does it really matter? www.sqlite.org says: 2004-Jun-30 - Version 3.0.2 (beta) Released But presumably it will be production-worthy before anyone else gets around to using nssqlite heavily anyway. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On Wed, Jul 14, 2004 at 07:47:57PM +0200, Wojciech Kocjan wrote: > Right, I never did write any license I release it on ;) It can be any > licence that doesn't imply licensing issues on sqlite itself (so I guess > GPL is out of question :-). Wojciech, SQLite is in the public domain, so any form of license conflict is impossible. You can release your nssqlite code under any license you want. http://www.sqlite.org/faq.html#q15 -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
...and for even simplier needs, there's always Berkeley DB: http://sleepycat.com/ - Nathan Dossy wrote on 7/14/04, 2:51 PM: > Also, for folks who want transaction-safe database but don't want to go > so far as to learn or use SQL, I'd like to remind folks about MetaKit: > > http://www.equi4.com/metakit.html > > The Tcl binding (Mk4tcl) is thread-safe and can be shared across threads > (with the -shared parameter to mk::file). -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On 2004.07.14, Talli Somekh <[EMAIL PROTECTED]> wrote: > > i think that if the goal of increasing AOLserver's use as a web > infrastructure, the inclusion of SQLlite is very important. PHP has > dropped MySQL and included SQLlite as the default DB because it is a > simple, small and self contained app for little websites. a NUKE app can > easily run off of it. Also, for folks who want transaction-safe database but don't want to go so far as to learn or use SQL, I'd like to remind folks about MetaKit: http://www.equi4.com/metakit.html The Tcl binding (Mk4tcl) is thread-safe and can be shared across threads (with the -shared parameter to mk::file). > so i think that including nssqllite and in fact pushing it as single > download for a complete web/db solution (with templating, db storage, > etc) it would be a very cool marketing win. Looking at http://www.sqlite.org/, I see: "SQLite version 3.0 is made possible in part by AOL developers supporting and embracing great Open-Source Software." I wonder what this is all about. Anyone know? And, from the FAQ at http://www.sqlite.org/faq.html: | (8) Is SQLite threadsafe? | | Yes. Sometimes. In order to be thread-safe, SQLite must be | compiled with the THREADSAFE preprocessor macro set to 1. In the | default distribution, the windows binaries are compiled to be | threadsafe but the linux binaries are not. If you want to change | this, you'll have to recompile. | | "Threadsafe" in the previous paragraph means that two or more | threads can run SQLite at the same time on different "sqlite" | structures returned from separate calls to sqlite_open(). It is | never safe to use the same sqlite structure pointer simultaneously | in two or more threads. | | Note that if two or more threads have the same database open and | one thread creates a new table or index, the other threads might | not be able to see the new table right away. You might have to get | the other threads to close and reopen their connection to the | database before they will be able to see the new table. | | Under UNIX, you should not carry an open SQLite database across a | fork() system call into the child process. Problems will result if | you do. Pargraph #3 bothers me. If this is the case (changes in one thread not picked up by the other threads unless they close/reopen the DB), that's a pretty tough limitation. SQLite deifnitely has its place, especially as an even lighter-weight alternative to MySQL, but I'd still urge folks to look at MetaKit, which has been around since 1996, compared to SQLite since 2000. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] [ 517267 ] Patch for SEGV if 401 redirect is used
In a message dated 7/13/2004 5:58:33 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: On Tue, Jul 13, 2004 at 05:14:05PM -0400, Dossy wrote:> Basically, the 3.x release is officially in support and maintenance> mode, and new development will should only be done in the 4.x tree.>> How do others feel about this?Sounds fine to me. As far as I'm concerned, 3.x became more or lessmaintainence only immediately once the AOLserver maintainers decidedto skip porting the 3.3+ad13 character set and other patches to 3.5.x,and to instead add that support only in 4.0.Given that we've already gone far down the path towards permanentlydeprecating 3.x, and that to date AFAIK no one has had any majorunaddressed complaints with 4.x, I'd rather see more effort go intogetting the many modules fully up to snuff for 4.x, and further 4.xwork in general, rather than backporting major changes to 3.x. Agreed -- let's stay focused on 4.x. -Jim -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
Andrew Piskorski wrote: If Wojciech doesn't want to support or maintain it, then yes, we can import it into SF CVS to make sure it's got a permanent place to Even if, hopefully, he does want to maintain it! Yes, as I said before - I can. I'd need to clean up the code, but when I tested it against 2.8.3, it was pretty stable (no memory leaks and a very nice speed). live. But, it depends on what license he released the code under whether we're allowed to do so or not. Oh, right, he didn't include any license in that beta tarball. Wojciech, could you tell us please if/how you want to license your code, if you'd like it kept in SourceForge CVS or not, etc.? Ok, I'll clean things up, license it as BSD. Does anyone know if sqlite 3.0.2 is stable or development release? I could try and adapt things to SQLite 3 since it looks like it supports datatypes. Anyone here is experienced with SQLite 3? (I use SQLite 2 extensively, but never dared to upgrade to 3.0 :) -- WK -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
Dossy wrote: Two people consitutes wide interest? :-) Two people asked. I wonder how many people would really be interested in nssqlite. If Wojciech doesn't want to support or maintain it, then yes, we can import it into SF CVS to make sure it's got a permanent place to live. But, it depends on what license he released the code under whether we're allowed to do so or not. Right, I never did write any license I release it on ;) It can be any licence that doesn't imply licensing issues on sqlite itself (so I guess GPL is out of question :-). Also I can support it if there is any interest. I did that as an experiment, never commented or documented anything, so it is far from being a nice package. Should I take some time to document things, clear the code up and do something about it? Is there any "wide interest" in using SQLite in AOLserver? BTW it also supports Tcl functions, I just don't remember how does it work :-) func_tcl.c has something to say on it ;) -- WK -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On Wed, Jul 14, 2004 at 12:39:51PM -0400, Dossy wrote: > > > nssqllite: http://www.panoptic.com/wiki/aolserver/157 > > > > This should go into SourceForge CVS, yes? It's clearly of wide > > interest... > > Two people consitutes wide interest? :-) Yes. SQLite is of wide interest as a light-weight RDBMS, and RDBMS stuff is of wide interest to users of AOLserver, therefore transitively... :) > If Wojciech doesn't want to support or maintain it, then yes, we can > import it into SF CVS to make sure it's got a permanent place to Even if, hopefully, he does want to maintain it! > live. But, it depends on what license he released the code under > whether we're allowed to do so or not. Oh, right, he didn't include any license in that beta tarball. Wojciech, could you tell us please if/how you want to license your code, if you'd like it kept in SourceForge CVS or not, etc.? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
Dossy wrote: Two people consitutes wide interest? :-) i think that if the goal of increasing AOLserver's use as a web infrastructure, the inclusion of SQLlite is very important. PHP has dropped MySQL and included SQLlite as the default DB because it is a simple, small and self contained app for little websites. a NUKE app can easily run off of it. so i think that including nssqllite and in fact pushing it as single download for a complete web/db solution (with templating, db storage, etc) it would be a very cool marketing win. talli -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On 2004.07.14, Andrew Piskorski <[EMAIL PROTECTED]> wrote: > On Wed, Jul 14, 2004 at 01:36:43PM +0200, Wojciech Kocjan wrote: > > I put up my attempts on www.zoro2.org/_chwilowe/nssqlite-beta.tar.gz - > > if anyone would like to write some docs or something, please do so. > > On Wed, Jul 14, 2004 at 09:58:41AM -0400, Dossy wrote: > > nssqllite: http://www.panoptic.com/wiki/aolserver/157 > > This should go into SourceForge CVS, yes? It's clearly of wide > interest... Two people consitutes wide interest? :-) If Wojciech doesn't want to support or maintain it, then yes, we can import it into SF CVS to make sure it's got a permanent place to live. But, it depends on what license he released the code under whether we're allowed to do so or not. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsjk2 is not mentioned on the wiki modules page
On 2004.07.14, Greg Wolff <[EMAIL PROTECTED]> wrote: > I just noticed that nsjk2 is not mentioned on the AOLserver wiki modules > page > http://www.panoptic.com/wiki/aolserver/160 It's listed on the Languages page: http://www.panoptic.com/wiki/aolserver/165 Maybe it's better to have all modules listed on the Modules page under the subheading "Languages" rather than having them on a separate page? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On Wed, Jul 14, 2004 at 01:36:43PM +0200, Wojciech Kocjan wrote: > I put up my attempts on www.zoro2.org/_chwilowe/nssqlite-beta.tar.gz - > if anyone would like to write some docs or something, please do so. On Wed, Jul 14, 2004 at 09:58:41AM -0400, Dossy wrote: > nssqllite: http://www.panoptic.com/wiki/aolserver/157 This should go into SourceForge CVS, yes? It's clearly of wide interest... -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] nsjk2 is not mentioned on the wiki modules page
I just noticed that nsjk2 is not mentioned on the AOLserver wiki modules page > http://www.panoptic.com/wiki/aolserver/160 /pgw -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
On 2004.07.14, Bas Scheffers <[EMAIL PROTECTED]> wrote: > > Has anyone done any work in integrating SQLite with the ns_db api? nssqllite: http://www.panoptic.com/wiki/aolserver/157 RTFW. Read The Fine Wiki. :-) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] File access permission
Don't forget that the AOLserver Tcl process does a CD. It needs write privs to create a file. If you want it to write to a specific location name that in the open. /pgw Dossy Shiobara [EMAIL PROTECTED] wrote > On 2004.07.14, Wei Shi <[EMAIL PROTECTED]> wrote: > > Say if I want to write something into a file on server, how can I do that? > > I used "open filename a" and I got error: "couldn't open "filename": > > permission denied". > > > > If not considering security issues, what's the easiest way of opening a > > file with write permission on server side? > > Using [open] is probably the easiest way. Just make sure you're writing > to a directory that the server has permission to write to. > > -- Dossy -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] [ 517267 ] Patch for SEGV if 401 redirect is used
BNA has upgraded its production servers to AOLserver v4.0.1 and does not use any 3.x servers. We are fine with your suggestion. /pgw Dossy <[EMAIL PROTECTED]> Sent by: AOLserver Discussion <[EMAIL PROTECTED]> 07/13/2004 05:14 PM Please respond to AOLserver Discussion To: [EMAIL PROTECTED] cc: (bcc: Greg Wolff/BNA Inc) Subject:[AOLSERVER] [ 517267 ] Patch for SEGV if 401 redirect is used John wrote in SF Bug #517267: > Has AOLserver 3.x been abandoned in terms of maintenance releases? > It's my impression that 4.x isn't stable, especially given that > critical modules (well, nsopenssl at least...) are still considered > "beta" in their AOLserver 4.x incarnations. And of course AOL is > still using 3.4.2. This is a great question. How long should we support the 3.x release? The 4.0 tree is already up to 4.0.5 with 4.0.6 just days away. The 4.0 tree has been considered stable and production-ready for a while now, but as John points out, AOL has been slow to upgrade all its servers to 4.0. While I'm not terribly enthusiastic about the idea, I'm okay with backporting significant bug fixes to 3.x. However, I am against the idea of fulfilling any RFE's in 3.x -- the 3.x tree at this point should be considered feature-frozen and no new features will go into it. Basically, the 3.x release is officially in support and maintenance mode, and new development will should only be done in the 4.x tree. How do others feel about this? Are there other bugs that need to be fixed in 3.x, other than #517267? (Including the ones fixed in 4.x that haven't been backported to 3.x yet?) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] SQLite
Bas Scheffers wrote: Hi, Has anyone done any work in integrating SQLite with the ns_db api? Might be an interesting project for 2 reasons: 1) There will be a simple DB again right out of the box, like the Illustra days and 2) it will be easy to write smaller, packaged apps that run out of the box on a plain vanilla AOLserver install, probably attracting new souls to the cause. Yes, I did that some time ago. It works, should be quite stable and handles schema changes without throwing an error (that is a quick hack involving doing all the query, storing it in memory and sending rows back without querying SQLite). I also did code to call Tcl functions from within SQLite. Unfortunately, I am low on time and C skills, otherwise I would give it a go soon myself... I put up my attempts on www.zoro2.org/_chwilowe/nssqlite-beta.tar.gz - if anyone would like to write some docs or something, please do so. ps. PHP5 also has sqlite. -- WK -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] SQLite
Hi, Has anyone done any work in integrating SQLite with the ns_db api? Might be an interesting project for 2 reasons: 1) There will be a simple DB again right out of the box, like the Illustra days and 2) it will be easy to write smaller, packaged apps that run out of the box on a plain vanilla AOLserver install, probably attracting new souls to the cause. Unfortunately, I am low on time and C skills, otherwise I would give it a go soon myself... Cheers, Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
