Hi folks,
I know its been posted there, but I personally feel at least one of these
individuals should come from the OpenACS community. I suspect we're a fairly
significant 'other' project that depends heavily on it, and as its firmly
part of future OpenACS strategy that kinda makes sense.
This sounds like your trying to create something very like what we have in
the OpenACS i.e. the forms API and ad_page_contract. Both of which provide
extensive and well organised facilites for doing this.
Much of what goes on in the OpenACS' request broker is not database specific
or
Title: Message
If anyone
from the OpenACS community would like to nominate themselves, please send your
brief paragraph or two to Nathan.
/s.
-Original Message-From: AOLserver
Discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Simon
MillwardSent: Tuesday, November 05,
On Tue, 5 Nov 2002, Simon Millward wrote:
This sounds like your trying to create something very like what we have
in the OpenACS i.e. the forms API and ad_page_contract. Both of which
provide extensive and well organised facilites for doing this.
Much of what goes on in the OpenACS' request
Daniel,
I'm surprised you say that, unless I'm missing what your trying to achieve.
OpenACS has numerous mechanisms an opportunities for data validation. The
ad_page_contract section offers a series of ways to restrict, validate and
correct data posted between pages. The newer forms API
Hi,
I just had my production AOLserver croak on me. After driving
the load up on the box to about 18.0 (on a 4-way E3800) it spat
this out in the server.log:
alloc: invalid block: ff2bb898: ff 70 0
alloc: invalid block: ff2bb898: ff 70 0
Then nsd died.
The error is coming from Tcl's
On Tuesday 05 November 2002 16:59, you wrote:
I'm on Solaris 2.8, AOLserver 3.5.0 and Tcl 8.4.1, gcc 2.95.3.
You're sure you do not have any corpses of libtcl8.4.so build with
some alpha release (Tcl8.4.0a4 or earlier) lying arround, eventually
picked by the DSO loader?
Just to make sure,
On 2002.11.05, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
On Tuesday 05 November 2002 16:59, you wrote:
I'm on Solaris 2.8, AOLserver 3.5.0 and Tcl 8.4.1, gcc 2.95.3.
You're sure you do not have any corpses of libtcl8.4.so build with
some alpha release (Tcl8.4.0a4 or earlier) lying arround,
On Tuesday 05 November 2002 17:25, you wrote:
Just to make sure, because the bugreport you're reffering to is
considered fixed and the 8.4.1 has the patch already applied.
That's why I'm asking. :-)
Another try...
Do you use clock format ... -gmt 1 somewhere in your Tcl code?
On Mon, 4 Nov 2002, Scott Goodwin wrote:
Hi Daniël,
Yes, this would be useful, maybe as a standard ns_* style command,
something like an ns_bind_vars.
Right now the focus is on setting up a core AOLserver team, getting
AOLserver 3.5.0 fully documented, getting the current modules cleaned
Sure. I'm not going to say that a number of packages and areas of code
aren't subject to fairly bad practice. Theres a lot of work gone into
getting the core of the system right, and i accept there's still quite a
bit to do going forward with many of the packages.
However, in principle at least
On Tuesday 05 November 2002 18:06, you wrote:
Another try...
Do you use clock format ... -gmt 1 somewhere in your Tcl code?
clock format, but not with -gmt 1.
Hm, first line of defence did not hold :(
So, somebody is freeing (or reallocating) already freed
memory or just passing bogus
In a message dated 11/5/02 12:31:57 PM, [EMAIL PROTECTED] writes:
Just thought it might be worthwhile taking a look at least to the
principle of the way data validation in forms is handled via the 'form'
command/API.
If someone is willing to submit this as a slightly more formal request, the
On Tuesday 05 November 2002 18:06, you wrote:
Another try...
Do you use clock format ... -gmt 1 somewhere in your Tcl code?
clock format, but not with -gmt 1.
-- Dossy
Ahhh... can you fire up the server with gdb, put a break-point on
tclThreadAlloc.c:748 and give it a go? Maybe we'll see
On Tue, Nov 05, 2002 at 03:43:42PM +0100, Daniël Mantione wrote:
Hmmm. At least OpenACS does not use it itself very well, I've yet to see
an example of a page that does verify it's input data...
On Tue, Nov 05, 2002 at 02:53:15PM +, Simon Millward wrote:
Daniel,
I'm surprised you say
I originally used the AOLSERVER (and NaviServer) back in the
mid-1990's and was wondering if I should bother to try it out
on the new Linux distributions or if there is a better mousetrap.
I'm hoping to do some medically related object file parsing and
I remember that the illustra ordb had some
On 2002.11.05, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
Do you have any home-brewn C-level extensions loaded?
Or, better yet, what extensions do you have loaded?
Nope. The only thing that's loaded is nssock. No nslog
even!
It's a series of Tcl proc's, some of which get registered as
On 2002.11.05, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
On Tuesday 05 November 2002 18:06, you wrote:
Another try...
Do you use clock format ... -gmt 1 somewhere in your Tcl code?
clock format, but not with -gmt 1.
-- Dossy
Ahhh... can you fire up the server with gdb, put a
I was asking if you would be able to sign up for any tasks as they come
up. Right now if you can identify a man page to document that hasn't
been signed up for yet, we could use your help there. Go to the
SourceForge Tasks section, Documentation. We're signing up for man pages
by file (ns_sock.n
On Tuesday 05 November 2002 20:34, you wrote:
The best I can do is hope to get a usable corefile next time this
happens.
Please do!
In the meantime, I will try to exercise the 3.5.0/8.4.1 with Purify
over the weekend. Maybe this will bring some results.
Thanks,
Zoran
On 2002.11.05, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
On Tuesday 05 November 2002 20:34, you wrote:
The best I can do is hope to get a usable corefile next time this
happens.
Please do!
In the meantime, I will try to exercise the 3.5.0/8.4.1 with Purify
over the weekend. Maybe this
On Tuesday 05 November 2002 20:32, you wrote:
Extensive use of nsv's to persist memory in the running nsd,
and the ns_schedule_proc'ed periodically goes through the
memory stored in nsv's and persists it to disk and nsv_unset's
things.
Shouldn't be a problem at all.
The problem is
In a message dated 11/5/2002 2:56:05 PM Eastern Standard Time, [EMAIL PROTECTED] writes:
That'll be cool. Set something up to ns_schedule_proc -thread and see
if your thread creation/cleanup shows anything funny going on. Throw in
lots of nsv_set and nsv_unset in there.
I'm going to get a copy
Title: Message
I've
been setting up a framework within which to consistently fit automated test
scripts. I'm using nsopenssl as my first example. I will releasethe
frameworkas soon as it is fully functional for community review and
comment. Some features: It compiles all source code,
On Tuesday, November 5, 2002, at 03:21 PM, Scott S. Goodwin wrote:
Don't let this stop you from writing manual or automated tests -- it
should be fairly straightforward to migrate that code into the framework.
Or from using other quality management tools than testing -- those get
forgotten a
25 matches
Mail list logo
