Re: [AOLSERVER] Ns_SetRequestAuthorizeProc has no Tcl Command
> This very thread is the proof that there is need for this, or? > Is this a good enough for you? Necessity is the mother of invention. Proof that there is need for this would be that someone has already implemented it, regardless of whether they make their implementation publically available. Having discussion threads about feature requests isn't proof that the features are necessary. :-) To bring one usage that is probably right around the corner is web services and machines communicating without user participation. One actual usage of this is the new ATOM API that is looking to supplement RSS and aggregation. Some background links on this are: http://bitworking.org/news/New_AtomAPI_Implementation_Release2 http://dannyayers.com/archives/001464.html http://www.intertwingly.net/wiki/pie/CommentAuthentication I can see where a lot of web services want more than simple AUTH but don't want to deal with the client side coding of SSL in their tools so digest seems at least a little better. As for implementing digest in AOLserver Rob Mayoff has already done the MD5 proc in his utils package here: http://dqd.com/~mayoff/aolserver/src/dqd_utils-1.3/ Anyway I see digest being a popular comprimise in alot of the client tools that will start to make themselves visible and if AOLserver wants to interact with these it may need it for web services. Best Regards, Carl Garland PS: Thanks to Nathan Folkman and others I will be starting at AOL for a contracting position very soon and look forward to being able to better serve both AOL and the AOLserver community. _ From Beethoven to the Rolling Stones, your favorite music is always playing on MSN Radio Plus. No ads, no talk. Trial month FREE! http://join.msn.com/?page=offers/premiumradio -- 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] ns_conn Parameters
Folks I've noticed that in some code examples like the showhdrs example in the docs http://aolserver.com/docs/devel/tcl/tcl-examples.html ns_conn has a $conn parameter passed to it e.g [ns_conn headers $conn]. This parameter isn't documented (that I can find) so I'm wondering if its still current and if it is then whats its purpose and is it important? Is there a kind sole out there who can enlighten me? TIA Steve Steve Manning - Linux Mandrake 9.0 - Gnome 2.0 East Goscote - Leicester - UK +44 (0)116 260 5457 E-Mail: [EMAIL PROTECTED] - Web: www.festinalente.co.uk AIM: verbomania - Public Key: 25665CAF from: wwwkeys.pgp.net There are only 10 types of people in this world Those who understand binary and those who don't -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On Mon, 2003-11-03 at 19:09, Tim Moss wrote: There's a number of modules out there that are in varying states of release - I've lost count of how many pure Tcl, pure C or hybrid session management modules I found, before deciding to refactor the OpenACS version. I too have written my own session management through filters and I would think a large number of developers have. For my sins I also have to develop sites in JBoss/Tomcat and one thing that is noticeable is that Tomcat has session management built in with authentication (through simple password files, db tables or LDAP) and authorisation through roles. These features are missing from the AOLserver API and I find that a bit strange given that its an application server and there can be very few applications which don't require some form of session, authentication and authorisation. Having said that, writing the session filter was one of the most enjoyable bits of coding I've done in a while so perhaps I shouldn't complain although I possibly need to get out more. Steve Steve Manning - Linux Mandrake 9.0 - Gnome 2.0 East Goscote - Leicester - UK +44 (0)116 260 5457 E-Mail: [EMAIL PROTECTED] - Web: www.festinalente.co.uk AIM: verbomania - Public Key: 25665CAF from: wwwkeys.pgp.net There are only 10 types of people in this world Those who understand binary and those who don't -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
Good ideas, and things we've talked about in the past. There's a new version of the AOLserver statistics Web interface for 4.0 being finished that will be released soon as well. - Nathan Tim Moss wrote on 11/4/03, 11:51 AM: > Once you've done this it would be nice if www.aolserver.com became an > 'example' site for new users. > The code, config, adp pages, etc. etc. should be accessible in CVS. > > This could demonstrate good practice usage of the core AOLserver > features, > perhaps some of the more commonly used modules, and perhaps some ideas on > how AOL goes about scaling AOLserver up to support the high levels of > traffic it can handle. > > AOL must have a whole raft of monitoring, debugging, performance analysis > tools for AOLserver. It would be nice if some of these made their way > into > the public domain too! ;-) > > Tim -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
Once you've done this it would be nice if www.aolserver.com became an 'example' site for new users. The code, config, adp pages, etc. etc. should be accessible in CVS. This could demonstrate good practice usage of the core AOLserver features, perhaps some of the more commonly used modules, and perhaps some ideas on how AOL goes about scaling AOLserver up to support the high levels of traffic it can handle. AOL must have a whole raft of monitoring, debugging, performance analysis tools for AOLserver. It would be nice if some of these made their way into the public domain too! ;-) Tim > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED] Behalf > Of Nathan Folkman > Sent: Tuesday, November 04, 2003 3:46 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] Ns_SetRequestAuthorizeProc has no Tcl Command > > > We're working on moving www.aolserver.com to one of our own servers > again, which would be obviously an AOLserver. Once the move is > completed, should be trivial to setup the TIP code there. > > - Nathan > > Zoran Vasiljevic wrote on 11/4/03, 10:32 AM: > > > Whatever the name, what I'd like to know is how the www.aolserver.com > is working to be able to fit-in the TIP-tracker once I get it from Tcl > people. > Who is attending the site? Whom should I bug? > > Zoran -- 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] AOLserver Improvement Proposals
On 2003.11.04, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > Because nothing comes for free and the best way to start something is > to pull up the sleeves and make it happen (with the hope that others > will follow) I will try to arrange that TIP-tracking infrastructure > gets somehow installed on the AOLserver website. No idea how am I > going to do this but I will try... This might seem low-tech, but I think it should suffice ... Folks can write up AIPs on the Wiki. This way, anybody can go in and edit, add comments, etc. http://panoptic.com/wiki/aolserver/AOLserverImprovementProposals I've started out by pretty much cutting and pasting TIP #2 as our AIP #1 -- someone needs to go in and revise it to make it relevant to AOLserver issues. Worry less about the formatting and more about what's actually being said on the wiki. I can enhance the wiki to make formatting improvements if this actually gets used. -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On Tuesday 04 November 2003 16:45, you wrote: > We're working on moving www.aolserver.com to one of our own servers > again, which would be obviously an AOLserver. Once the move is > completed, should be trivial to setup the TIP code there. Great! Thanks Nathan! In the meantime I'll try to get the TIP-stuff from Donal from Tcl core. And, AEP (= AOLserver Enhancement Proposal), if nobody objects, should be the name of this child. Cheers Zoran -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
We're working on moving www.aolserver.com to one of our own servers again, which would be obviously an AOLserver. Once the move is completed, should be trivial to setup the TIP code there. - Nathan Zoran Vasiljevic wrote on 11/4/03, 10:32 AM: > Whatever the name, what I'd like to know is how the www.aolserver.com > is working to be able to fit-in the TIP-tracker once I get it from Tcl > people. > Who is attending the site? Whom should I bug? > > Zoran -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On Tuesday 04 November 2003 16:33, you wrote: > How about "APE" (AOLserver Proposed Enhancement)? :-) Seriously though, > this is a great idea to help us better collect, review, and implement a > lot of the great ideas being generated in the Community. > Whatever the name, what I'd like to know is how the www.aolserver.com is working to be able to fit-in the TIP-tracker once I get it from Tcl people. Who is attending the site? Whom should I bug? Zoran -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
How about "APE" (AOLserver Proposed Enhancement)? :-) Seriously though, this is a great idea to help us better collect, review, and implement a lot of the great ideas being generated in the Community. - Nathan Zoran Vasiljevic wrote on 11/4/03, 9:29 AM: > I must add to this that the AIP (= AOLserver Improvement Proposal) > should address the *general* plugin interface of AOLserver, more > specifically the interface used to hook-up alternate authorization > methods when/if they come along the road. The Jim's fine idea can > serve as the starting point. -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On Tuesday 04 November 2003 15:07, you wrote: > On 2003.11.04, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > > People write TIP's. Core team decides what/what-not. > > Simple as that. > > [...] > > > Now, what do you say about that? > > Sure, of course it's a good idea. The person(s) who most want to see > Digest auth can bear the burden of writing the AIP for it. :-) > Oh boy, I'm glad we're (finally) becoming more constructive! I must add to this that the AIP (= AOLserver Improvement Proposal) should address the *general* plugin interface of AOLserver, more specifically the interface used to hook-up alternate authorization methods when/if they come along the road. The Jim's fine idea can serve as the starting point. This is not the only part, though... I think there is a patch from Joshua Ginsberg <[EMAIL PROTECTED]> to allow for some more info for module developers about the state of the http connection, right? And there is a proposal from Vlad Seryakov <[EMAIL PROTECTED]> to decouple http processing in order to make AS more general vehicle for writing non-http-related services. And, I'm sure there are *lots* of other ideas for which there should be an AIP to vote for/aginst, as well. If nobody objects Because nothing comes for free and the best way to start something is to pull up the sleeves and make it happen (with the hope that others will follow) I will try to arrange that TIP-tracking infrastructure gets somehow installed on the AOLserver website. No idea how am I going to do this but I will try... Zoran -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On 2003.11.04, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > People write TIP's. Core team decides what/what-not. > Simple as that. [...] > Now, what do you say about that? Sure, of course it's a good idea. The person(s) who most want to see Digest auth can bear the burden of writing the AIP for it. :-) -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On Tuesday 04 November 2003 13:41, you wrote: > I personally don't want to see AOLserver become a collection trivial to > implement features that a small subset of the user community wants > and/or needs. I have no problem with that. This is also my view on the matter. Although I would not consider this topic to be of use for a small subset of the user community. I might be wrong, though... But, why don't we simply change this boring and fruitless discussion to something more constructive? I have proposed a TIP-like mechanism some time ago. Why not follow the successful Tcl way of handling such issues, instead of wasting people's time and list-bandwidth like in this (or perhaps future) case? People write TIP's. Core team decides what/what-not. Simple as that. More constructive, more formal and with an audit trail, so nothing is lost. Works fine in Tcl. We can borrow the TIP implementation from the friendly Tcl project. I'm sure they will have no problem with that. Now, what do you say about that? Zoran -- 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On 2003.11.04, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > > This very thread is the proof that there is need for this, or? > Is this a good enough for you? Necessity is the mother of invention. Proof that there is need for this would be that someone has already implemented it, regardless of whether they make their implementation publically available. Having discussion threads about feature requests isn't proof that the features are necessary. :-) > Digest auth or not, if we can bring AS to be more versatile > with *minimal* effort, what not doing this? I personally don't want to see AOLserver become a collection trivial to implement features that a small subset of the user community wants and/or needs. If someone has the spare time to make the change Jim suggested and do all the necessary regression testing to ensure that normal request processing isn't broken by the change ... maybe their time would be better spent improving the DB API or something that's more generally useful to the majority of AOLserver users? > I really do not undersand the point of this thread any more. I'm not sure there was a point in the first place. As you pointed out, this very same discussion happened nearly two years ago, and we still have nothing more than Basic auth. and the community as a whole seems to have survived without much complaint. Perhaps that's a sign ... -- 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] nsd binding to > 1 port?
Scott Laplante said: > Our internal messages among different servers in our cluster are > currently having to wait for a free connection thread, and in times of > high traffic, this backup causes rather critical problems. Not sure as I haven't used custom threads yet, but this is what I would probably try: In init.tcl, you could start another threat. It seems to me what you are doing doesn't require a pool of threads, so simple plain Tcl server socket and non-blocking io should do the trick. Make sure this thread doesn't exit on error and you can also have a scheduled proc checking if it is still alive periodicaly. 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] Ns_SetRequestAuthorizeProc has no Tcl Command
On Tuesday 04 November 2003 03:37, you wrote: > On 2003.11.03, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > > I think there is a need for a better solution. > > Is this what you are willing to discuss? > > Yes and no. What I'm willing to discuss is if there is a need for /a/ > solution. Then, we can talk about better ones ... This very thread is the proof that there is need for this, or? Is this a good enough for you? Besides, I'm not that phylosophical about the matter. I see this really pragmatically: AS has some internal "limitations" (or call this like you'd like) which can be trivially rectified. If we have to discuss this triviality *that long*, than I'm really afraid what would happen if some major change should be discussed? We'd be totally paralized and would just run in circles, with time passing by... This is a highly sensitive matter and could bring to a show-stop for an open source project. This project has already experienced a fork, but thanks to some nice people at AOL, everything is in place for some time again. BTW, I'm also in the Tcl development group. If we were to discuss all minor changes that *much* and that *long* we'd be still sitting on Tcl 7.4. Digest auth or not, if we can bring AS to be more versatile with *minimal* effort, what not doing this? I really do not undersand the point of this thread any more. Zoran -- 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.
