Cookies require a P3P header now?
Yes, the default security prefs as of IE6 are to discard cookies at
exit that don't have a compact privacy declaration indicating that
you won't share their information with anyone.
Ever wonder why some sites seem to forget your cookies, and some are
incredible at remembering them? The P3P header is the reasons.
I can't prove it yet, but there's some situation that causes ns_db
handles to not get cleaned up. It only happens in production, not
under an "ab" test harness. I solved it by manually releasing all my
db handles and wrapping catch{} statements around everything. It
might be "adp flush failed" "abort exception raised" -- or maybe some
other exception.
Which database are you using? I seem to remember that not all
database drivers
reset after a conn closes.
Vlad's Berkeley DB driver nsdbbd. Stable under stress testing with
"ab" but in the real world, I'm getting handle-not-released problems.
I have my own db api which uses an ns_atclose to cleanup/rollback
anything not
released. In fact, I never release a handle in a script, that is
what the
ns_atclose call is for.
Interesting that you use ns_atclose, why not use the default
mechanism, which is registered with ns_db ? Like so:
static Ns_DbProc dbProcs[] = {
{DbFn_ServerInit, DbServerInit},
{DbFn_Name, DbName},
{DbFn_DbType, DbDbType},
{DbFn_OpenDb, DbOpenDb},
{DbFn_CloseDb, DbCloseDb},
{DbFn_DML, DbDML},
{DbFn_GetRow, DbGetRow},
{DbFn_Flush, DbFlush},
{DbFn_Cancel, DbCancel},
{DbFn_Exec, DbExec},
{DbFn_BindRow, DbBindRow},
{DbFn_ResetHandle,DbResetHandle},
{0, NULL}
};
or is it just the case that you're not using ns_db at all, and wrote
your own?
Catch ends up being a much worse problem than anything else I've
ever used in
tcl. It effectively removes most/all error information, so you
cannot track
down a bug. Also, if a catch is around code which doesn't compile,
the error
message you get is usually completely unrelated to the actual error.
Yeah, I definitely don't like manually releasing all my handles, but
it solves the problem, and when you're in production...
-john
--
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.
