Re: [AOLSERVER] Best way for user authentication?
Jeremy, Why re-invent the wheel? OpenACS already does this and much more and it's all open source. Take a look at www.openacs.org for more code than you can shake a stick at! Brian -Original Message- From: Jeremy Cowgar [mailto:[EMAIL PROTECTED] Sent: 15 March 2003 16:01 To: [EMAIL PROTECTED] Subject: [AOLSERVER] Best way for user authentication? Please forgive my ignorance, But can someone point me in a direction for user authentication with AOL server? I understand two methods, but not certain how to make it all glue together. The first method I know is http authentication which will pop up a dialog box and ask the user for their information. I would like to try to avoid this because it's not quite as user friendly as having a login form. The second method is using cookies. I can handle this, but ensuring that the cookie is read for all .adp requests, that it is available in all my tcl methods, in the included adp_ files, etc... that is confusing me a little. I am certian their are other ways as well. Can anyone give me a little info or point me to an information source on this subject? Thanks, Jeremy I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Emacs and ADP -- a solution
I use UltraEdit(www.ultraedit.com) as you can write your own syntax highlighting filters. I'm not saying its the best - its what I've used for a while and I'm now used to it. -Original Message-From: AOLserver Discussion [mailto:[EMAIL PROTECTED]On Behalf Of Kevin LawverSent: Monday, March 17, 2003 2:22 PMTo: [EMAIL PROTECTED]Subject: Re: [AOLSERVER] Emacs and ADP -- a solutionjEdit (www.jedit.org). It does a good job of markup highlighting, and works on all four platforms I use. It comes with all kinds of code highlighting presets built in, and handles pretty much everything I've thrown at it without dying. KevinIn a message dated 3/17/03 9:19:25 AM, [EMAIL PROTECTED] writes: What does everyone else use for editing ADP's? TCL for that fact as well.JeremyOn Sunday 16 March 2003 08:39 am, you wrote: Greetings. I use emacs for all text editing and I was running into a problem with editing ADP's. With html-helper-mode I can do things like narrow down to a _javascript_ block and edit _javascript_ with a _javascript_ mode (syntax highlighting, language helpers, automatic indenting, etc...). I wished to have the same thing for editing Tcl blocks in my .adp's % ... %. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Origins of the SQL features of the AOLServer API?
From: Bas Scheffers [EMAIL PROTECTED] IIRC, there is a project on sourceforge bringing AOLserver db connectivity to standard Tcl, but their search functionality is currently down. What: nstcl Where: URL: http://michael.cleverly.com/nstcl URL: http://michael.cleverly.com/nstcl/nstcl-1.0.tz Description: Tcl package that implements the AOLserver's ns_db API. The current version supports Oracle 8 (by wrapping calls to Oratcl 3.0), Postgres 7 (via pgtclsh), and Solid (via Soltcl). Uses MIT/X11 license. The current version is 1.0 . Updated: 08/2002 Contact: URL: mailto:[EMAIL PROTECTED] (Michael A. Cleverly) Is this the project to which you refer? -- Tcl - The glue of a new generation. URL: http://wiki.tcl.tk/ Larry W. Virden mailto:[EMAIL PROTECTED] URL: http://www.purl.org/NET/lvirden/ Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -- -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
Indeed. I've grabbed the security code alone from OpenACS and got that working with AOLserver and PostgreSQL with just a few minor changes necessary (it about 20 of the .tcl files from OpenACS). At the time OpenACS wouldn't install and I was unsure about taking on the whole OpenACS framework if I didn't need it What I've got is not very clean: there's probably buckets of unused procs and I'm sure quite a few files could be dropped completely if I spent some time further modifying the code. It was really an exercise to see how easy/hard it was to take OpenACS code and backport it to a vanilla AOLserver installation, but also partly driven by the need to find an extensive, well tested, performant, session management and security system. I'm more than happy to share what I've got with you (under all the normal GPL/MPL rules and regulations of course, since I didn't write the code of course), but can't spend a huge amount of time documenting it or whatever. Tim -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf Of Brian Fenton Sent: Tuesday, March 18, 2003 10:12 AM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] Best way for user authentication? Jeremy, Why re-invent the wheel? OpenACS already does this and much more and it's all open source. Take a look at www.openacs.org for more code than you can shake a stick at! Brian -Original Message- From: Jeremy Cowgar [mailto:[EMAIL PROTECTED] Sent: 15 March 2003 16:01 To: [EMAIL PROTECTED] Subject: [AOLSERVER] Best way for user authentication? Please forgive my ignorance, But can someone point me in a direction for user authentication with AOL server? I understand two methods, but not certain how to make it all glue together. The first method I know is http authentication which will pop up a dialog box and ask the user for their information. I would like to try to avoid this because it's not quite as user friendly as having a login form. The second method is using cookies. I can handle this, but ensuring that the cookie is read for all .adp requests, that it is available in all my tcl methods, in the included adp_ files, etc... that is confusing me a little. I am certian their are other ways as well. Can anyone give me a little info or point me to an information source on this subject? Thanks, Jeremy I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Netscape-Brew
Hello, I noticed that aolsearch.aol.com recently switched from AOLserver to a web server that identifies itself as Netscape-Brew. Does anyone know what Netscape-Brew is? -ayan -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
Why re-invent the wheel? OpenACS already does this and much more and it's all open source. Take a look at www.openacs.org for more code than you can shake a stick at! My experience with OpenACS was that it is much more difficult to develop modules for if it's simply going to be an application for inhouse use (not redistributing it) and also that the speed of AOL Server is severly hit. Is this the case or do I have a special case? Jeremy -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
On Tue, Mar 18, 2003 at 09:26:49AM -0500, Jeremy Cowgar wrote: Why re-invent the wheel? OpenACS already does this and much more and it's all open source. Take a look at www.openacs.org for more code than you can shake a stick at! My experience with OpenACS was that it is much more difficult to develop modules for if it's simply going to be an application for inhouse use (not What? Why would developing an in-house only app be any harder than developing one suitable for redistribution to others? In reality, the opposite is true. If you're the only user than you can take shortcuts and in general things are simpler and easier. Or did you mean that using OpenACS at all is much more work for you than not? There is a sizeable learning curve to taking full advantage of the OpenACS features. But, no one's forcing you to take advantage of them. You can safely ignore the vast majority of the complexity when you start out, if you so wish. Lots of the functionality you just get for free with basically no effort on your part - user registration, session management, etc. I can't imagine it ever being FASTER to build any sizeable application from scratch with just the plain AOLserver APIs than with OpenACS. Perhaps a different toolkit would fit your desires better (not that I'd know why), or you'd not want to use OpenACS for some other reason, but faster development time with no additional toolkit at all, than with the OpenACS toolkit? I don't think so. That would be a truly damning indictment of OpenACS if true, but fortunately, it's not even remotely the case. -- Andrew Piskorski [EMAIL PROTECTED] http://www.piskorski.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
This is interesting. OpenACS has recently greatly increased is speed. Also AOLserver 4 is faster, so the performance should be less of an issue. I am surpised that you though development speed was reduced. I find that the greatest asset of OpenACS. It is a complex system, and there is definitely a learning curve though. Dave On Tue, Mar 18, 2003 at 09:26:49AM -0500, Jeremy Cowgar wrote: Why re-invent the wheel? OpenACS already does this and much more and it's all open source. Take a look at www.openacs.org for more code than you can shake a stick at! My experience with OpenACS was that it is much more difficult to develop modules for if it's simply going to be an application for inhouse use (not redistributing it) and also that the speed of AOL Server is severly hit. Is this the case or do I have a special case? Jeremy -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- Dave Bauer [EMAIL PROTECTED] http://www.thedesignexperience.org -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
Jeremy Cowgar said: redistributing it) and also that the speed of AOL Server is severly hit. Is this the case or do I have a special case? When you use a generic tool, that will always be the case, unless you are a seriously bad programmer. I never really used OpenACS, but looking at ACS 4, the motto of everything in the database seemed to get a little counter productive. Yes, the database did it in less CPU cycles then DB+AOLserver, but it put more strain on the DB then needed and while adding more webservers should be trivial, maintaining a database cluster or moving your database to bigger machines all the time as you grow is a major PITA. I wonder if OpenACS is like that too. Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
On Tuesday, March 18, 2003, at 09:54 AM, Dave Bauer wrote: This is interesting. OpenACS has recently greatly increased is speed. Also AOLserver 4 is faster, so the performance should be less of an issue. I am surpised that you though development speed was reduced. I find that the greatest asset of OpenACS. It is a complex system, and there is definitely a learning curve though. Dave This is great news! What areas did you see the greatest amount of performance improvement? - Nathan -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] OpenACS
My experience with OpenACS was that it is much more difficult to develop modules for if it's simply going to be an application for inhouse use (not What? Why would developing an in-house only app be any harder than developing one suitable for redistribution to others? In reality, the opposite is true. If you're the only user than you can take shortcuts and in general things are simpler and easier. You are right and that's what I was trying to say. There is a sizeable learning curve to taking full advantage of the OpenACS features. But, no one's forcing you to take advantage of them. You can safely ignore the vast majority of the complexity when you start out, if you so wish. Lots of the functionality you just get for free with basically no effort on your part - user registration, session management, etc. All users are added when their network account is setup. Session management is already complete (to the degree I need it) in about 90 lines of code (checks for a cookie, set's a cookie on login, etc...). I have no real need for session management other than knowing who is logged in (realitively simple). I can't imagine it ever being FASTER to build any sizeable application from scratch with just the plain AOLserver APIs than with OpenACS. Perhaps a different toolkit would fit your desires better (not that I'd know why), or you'd not want to use OpenACS for some other reason, but faster development time with no additional toolkit at all, than with the OpenACS toolkit? I don't think so. That would be a truly damning indictment of OpenACS if true, but fortunately, it's not even remotely the case. Maybe I need to reconsider OpenACS for another product I am working on in my spare time. Development really has not begun on it, I have been in the spec part of development and just recently trying to decide what is the best product for it. It's a community site which would require alot of what you were speaking about. I am trying to maximize effeciency though, that's my only concern. Jeremy -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
Dave Bauer said: I am surpised that you though development speed was reduced. I find that the greatest asset of OpenACS. It is a complex system, and there is definitely a learning curve though. Once you understand it, I guess it is fine. The reason there is a steep learning curve is because it is designed to be used with the default user interfaces (.tcl files), which you edit (or use templates) to make OpenACS look like you want it. _that_ is easy. Creating a custom homepage or a new module that uses authentication and permissions is horrible because the documentation just is not there. (http://openacs.org/api-doc/package-view?version_id=5) I don't see what is so hard about describing all your procedure in a way similar to Javadocs. It's a catch 22 situation for the developers; developers don't like doing docs, but they want as many people as possible to use it. Personaly, I would prefer a package that does not have and client-facing pages at all, only admin pages and a good API documentation. Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
Netscape-Brew is a platform based off NES.. Oli Bird Ayan George wrote: Hello, I noticed that aolsearch.aol.com recently switched from AOLserver to a web server that identifies itself as Netscape-Brew. Does anyone know what Netscape-Brew is? -ayan -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] OpenACS
On Tue, Mar 18, 2003 at 10:08:19AM -0500, Jeremy Cowgar wrote: All users are added when their network account is setup. Session management is already complete (to the degree I need it) in about 90 lines of code (checks for a cookie, set's a cookie on login, etc...). I have no real need for Then why are you asking? If you already did all the work to avoid using OpenACS, then of COURSE switching to OpenACS would be extra work, certainly counter-productive in the short term, and perhaps even counter-productive in the long term as well. Seems to me you are taking the work put into your existing system as given, and pretending you got all that for free, which ain't so. Maybe I need to reconsider OpenACS for another product I am working on in my spare time. Development really has not begun on it, I have been in the spec Ah, so your choice is not between no toolkit and the OpenACS toolkit, but between the in-house toolkit you used on a previous project, and the OpenACS toolkit. A very different issue. If you want advice, you should probably describe your specific needs and concerns re. OpenACS and ask for more details on the openacs.org forums. -- Andrew Piskorski [EMAIL PROTECTED] http://www.piskorski.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication? (a real answer!)
Simplest way that is also quite safe: Create sessions table (user_id, session_key, last_action_datetime). When a user logs in, you create a sessionkey (40 character random string will do) and store a row in the database table. You also set a cookie with the session key and make sure you use path=/, so it is returned to the server on all requests. When a user comes to the site, you always run a procedure (set up a trace?) to check for the cookie and the validity of the key found and update the session table with the current date and time. Unless ofcourse the date and time found was smaller then (current_date - session_timeout). And you display a timeout screen, and delete the row and the cookie. (path!) After a succesfull authentication you set a global variable with the user id or a value like -1 if it is not a valid user. Now your script can use this variable to know who is logged in or not. When a user logs out, simply delete the row and the cookie. You may also want to set op a process that at intervals clears out the session table for session that timed out. If you want a persistant login (remember me), you can add another column to your users table that holds another random string, also set in a cookie but this cookie is never deleted and set to never expire. You can check for this one if there is no real session key, but be sure to note it's use in another global variable so scripts can tell if this really isn't secure enough for the action they want to perform. If security is not a security issue at all, you could just go for the key in the users table and write that to a cookie when they log in with the correct answer and forget about the sessions table. Hope that helps, Bas. Brian Fenton said: Jeremy, Why re-invent the wheel? OpenACS already does this and much more and it's all open source. Take a look at www.openacs.org for more code than you can shake a stick at! Brian -Original Message- From: Jeremy Cowgar [mailto:[EMAIL PROTECTED] Sent: 15 March 2003 16:01 To: [EMAIL PROTECTED] Subject: [AOLSERVER] Best way for user authentication? Please forgive my ignorance, But can someone point me in a direction for user authentication with AOL server? I understand two methods, but not certain how to make it all glue together. The first method I know is http authentication which will pop up a dialog box and ask the user for their information. I would like to try to avoid this because it's not quite as user friendly as having a login form. The second method is using cookies. I can handle this, but ensuring that the cookie is read for all .adp requests, that it is available in all my tcl methods, in the included adp_ files, etc... that is confusing me a little. I am certian their are other ways as well. Can anyone give me a little info or point me to an information source on this subject? Thanks, Jeremy I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
Oliver Bird said: Netscape-Brew is a platform based off NES.. What, AOL runs on a Nintendo!? Lets hope at least it is a 16 bit one! (SNES) Oh, never mind you meant that one. Considering its saying version 6.2.1 it is probably iPlanet by now. :) Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] OpenACS
Then why are you asking? If you already did all the work to avoid using OpenACS, then of COURSE switching to OpenACS would be extra work, certainly counter-productive in the short term, and perhaps even counter-productive in the long term as well. Seems to me you are taking the work put into your existing system as given, and pretending you got all that for free, which ain't so. The answer which allowed me to develop the system I was talking about above originated from this thread. The answer that I used was posted on Saturday by Patrick Spence. The thread originally started on the 15th. I have not posted to it after Patrick helped me out, it has just continued to evolve from other people posting (which is great by the way). Ah, so your choice is not between no toolkit and the OpenACS toolkit, but between the in-house toolkit you used on a previous project, and the OpenACS toolkit. A very different issue. If you want advice, you should probably describe your specific needs and concerns re. OpenACS and ask for more details on the openacs.org forums. I have joined the OpenACS site. I will be playing with it some more these next few days. I do not have a in-house toolkit for use with AOL/Tcl systems. So it would be between a simple interface and OpenACS at this point in time. Jeremy -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
On Tue, Mar 18, 2003 at 10:08:14AM -0500, Nathan Folkman wrote: On Tuesday, March 18, 2003, at 09:54 AM, Dave Bauer wrote: This is interesting. OpenACS has recently greatly increased is speed. This is great news! What areas did you see the greatest amount of performance improvement? I hear Don Baccus sped up the permission system a lot in OpenACS 4.6.1. There a system-wide coherent API for cacheing of database info coming for 4.7, I think. I don't remember if there was any other important performance work or not, but apparently dotLRN in particular has been driving scalability work. In addition, there are some switches (e.g., performance mode) already implemented in the code that are easily toggled by the admin. There are also other tweaks that are known, but I think not yet implemented with any easy admin-flippable switch. E.g.: http://openacs.org/forums/message-view?message_id=78154 -- Andrew Piskorski [EMAIL PROTECTED] http://www.piskorski.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
Bas Scheffers wrote: Oliver Bird said: Netscape-Brew is a platform based off NES.. What, AOL runs on a Nintendo!? Lets hope at least it is a 16 bit one! (SNES) Somehow I can just picture that.. I'm sure we'll upgrade to a Dreamcast eventually, however. Oh, never mind you meant that one. Considering its saying version 6.2.1 it is probably iPlanet by now. :) Well.. sort of... it's the same back end as most of the AOL channels are. Then again, I didn't particularly enjoy having to shepherd any bits of AOLSearch from my beloved AOLserver to NS/Brew... :) Oli Bird -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
Easy now - there's no reason to bash NPE/NES. You may not have know this, but the AOLserver and NPE/NES Teams are now part of the same infrastructure group here at AOL. One our goals for the upcoming quarter is for both teams to better work together and to identify some areas where we can share code and experience. Since AOLserver continues to be managed as an Open Source project, you all should benefit from the cooperation between both teams as well. There are currently no plans to drop support for either platform, so I wouldn't read into production migrations from platform to platform. I'll try and keep everyone updated with what's going on with both teams over the next few months. - Nathan On Tuesday, March 18, 2003, at 11:05 AM, Oliver Bird wrote: Well.. sort of... it's the same back end as most of the AOL channels are. Then again, I didn't particularly enjoy having to shepherd any bits of AOLSearch from my beloved AOLserver to NS/Brew... :) Oli Bird -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] OpenACS
- Original Message - From: Jeremy Cowgar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 18, 2003 8:49 AM Subject: Re: [AOLSERVER] OpenACS Then why are you asking? If you already did all the work to avoid using OpenACS, then of COURSE switching to OpenACS would be extra work, certainly counter-productive in the short term, and perhaps even counter-productive in the long term as well. Seems to me you are taking the work put into your existing system as given, and pretending you got all that for free, which ain't so. The answer which allowed me to develop the system I was talking about above originated from this thread. The answer that I used was posted on Saturday by Patrick Spence. The thread originally started on the 15th. I have not posted to it after Patrick helped me out, it has just continued to evolve from other people posting (which is great by the way). I am glad I was able to help :) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
It's OK Nathan... I wasn't exactly serious... I do a lot of NPE development now as well, and enjoy it. My philosophy would be that each problem has its own solution - no server is the best for everything, but each is good at something. (yes, very new age, but it is at least correct) Oli Bird Nathan Folkman wrote: Easy now - there's no reason to bash NPE/NES. You may not have know this, but the AOLserver and NPE/NES Teams are now part of the same infrastructure group here at AOL. One our goals for the upcoming quarter is for both teams to better work together and to identify some areas where we can share code and experience. Since AOLserver continues to be managed as an Open Source project, you all should benefit from the cooperation between both teams as well. There are currently no plans to drop support for either platform, so I wouldn't read into production migrations from platform to platform. I'll try and keep everyone updated with what's going on with both teams over the next few months. - Nathan On Tuesday, March 18, 2003, at 11:05 AM, Oliver Bird wrote: Well.. sort of... it's the same back end as most of the AOL channels are. Then again, I didn't particularly enjoy having to shepherd any bits of AOLSearch from my beloved AOLserver to NS/Brew... :) Oli Bird -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
On 2003.03.18, Bas Scheffers [EMAIL PROTECTED] wrote: Oliver Bird said: Netscape-Brew is a platform based off NES.. What, AOL runs on a Nintendo!? Lets hope at least it is a 16 bit one! (SNES) Oh, never mind you meant that one. Considering its saying version 6.2.1 it is probably iPlanet by now. :) Or, Netscape Enterprise Server 6.2.1. We're still running Netscape Enterprise Server 3.63 in production at work ... fear. -- 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: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
Don Baccus said: Just because they're not on the openacs.org site (Dave, what's up with that?) doesn't mean they're not part of our toolkit! You had me fooled! Sounds almost like closed source CMS products, you can't see how it works untill you spent the money. ;-) (Although OpenACS has nothign to hide, ofcourse) I may just give it a go some time and see what's there. (Once I get my new house, adsl line and computer sorted out...) Cheers, Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Netscape-Brew
you won't really be running a powerhouse environment until you move to a set of clustered apple iigs web servers. although someone should really run some performance tests vs. the nintendo. sorry... off toaopic... --- Oliver Bird [EMAIL PROTECTED] wrote: Bas Scheffers wrote: Oliver Bird said: Netscape-Brew is a platform based off NES.. What, AOL runs on a Nintendo!? Lets hope at least it is a 16 bit one! (SNES) Somehow I can just picture that.. I'm sure we'll upgrade to a Dreamcast eventually, however. Oh, never mind you meant that one. Considering its saying version 6.2.1 it is probably iPlanet by now. :) Well.. sort of... it's the same back end as most of the AOL channels are. Then again, I didn't particularly enjoy having to shepherd any bits of AOLSearch from my beloved AOLserver to NS/Brew... :) Oli Bird -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ = Are you going to spend the rest of your life selling sugar water, or are you going to come with me and change the world? __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Best way for user authentication?
Bas Scheffers wrote: I don't see what is so hard about describing all your procedure in a way similar to Javadocs. Just because they're not on the openacs.org site (Dave, what's up with that?) doesn't mean they're not part of our toolkit! Download and install it and you'll see that the vast majority of procs *are* described in a way *very* similar to Javadocs. What we're missing are cookbook-ish style docs that set you through writing and customizing stuff. It's a catch 22 situation for the developers; developers don't like doing docs, but they want as many people as possible to use it. Traditionally we've been a very small team of volunteers. However over the last several months the team's been growing steadily and that includes a couple of people who have stepped up to work on documentation, in particular documentation to help people get started. We have several developers who don't mind doing docs, but that doesn't mean they always have time doing docs. While making our stuff available to as many people as possible is certainly a nice goal, for most of us our primary goal is to make sure we deliver working websites to our clients on time. Personaly, I would prefer a package that does not have and client-facing pages at all, only admin pages and a good API documentation. Wheels were made to be reinvented, true enough :) -- Don Baccus Portland, OR http://donb.photo.net, http://birdnotes.net, http://openacs.org -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Help with nsimap
I am having trouble with nsimap on a redhat 7.2 box. The nsimap.so
loads at startup OK and installs its garbage collector but when I try
to open a session from a tcl page using ns_imap open I get (with
debug logging turned on):
[18/Mar/2003:17:34:34][15182.5126][-conn2-] Debug: ns_imap: open:
0x8ca8f50: 1: {127.0.0.1}: [EMAIL PROTECTED]
Killed
By adding some more Ns_Log's I've isolated it down to this line (447
of nsimap.c):
if(!session-mailbox || !(session-stream =
mail_open(session-stream,session-mailbox,flags))) {
Which looks to me where nsimap calls the c-client code to open the connection.
The mail server logs show:
01:48:25.58 5 IMAP connection request from [127.0.0.1:41527], socket=27
01:48:25.58 4 IMAP-02446([127.0.0.1]) got connection on [127.0.0.1:143]
01:48:25.58 5 IMAP-02446([127.0.0.1]) out: * OK CommuniGate Pro IMAP
Server 4.0.6 at aliencamel.com ready\r\n
01:48:25.58 5 IMAP-02446([127.0.0.1]) inp: CAPABILITY
01:48:25.58 5 IMAP-02446([127.0.0.1]) out: * CAPABILITY IMAP4
IMAP4REV1 ACL NAMESPACE UIDPLUS IDLE LITERAL+ QUOTA ID MULTIAPPEND
LISTEXT CHILDREN AUTH=LOGIN AUTH=PLAIN AUTH=CRAM-MD5
AUTH=DIGEST-MD5\r\
01:48:25.58 5 IMAP-02446([127.0.0.1]) inp: 0001 AUTHENTICATE CRAM-MD5
01:48:25.58 5 IMAP-02446([127.0.0.1]) AUTH challenge:
[EMAIL PROTECTED]
01:48:25.58 5 IMAP-02446([127.0.0.1]) out: +
PDI0NDYuMTA0ODAzODUwNUBhbGllbmNhbWVsLmNvbT4=\r\n
01:48:25.60 3 IMAP-02446([127.0.0.1]) read failed. Error
Code=connection closed by peer
So it seems to be at the point of processing the AUTH challenge or
formulating the response. The mtest program provided with uw imap
sources works OK when they are used. I've used both a redhat rpm of
imap-devel and compiled up the uw imap sources and I get the same
problem in either instance.
It runs great on my Mac OS X development box. If anyone has any
suggestions on what could be happening or what I could do it would be
much appreciated.
Thanks
Matthew Walker
PS. If I run strace I get:
15911 getppid() = 15908
15911 poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, 2000) = 1
15911 getppid() = 15908
15911 read(3, \0\374\337\276\0\0\0\0\274\320\337\276\20\237\21\10
\310..., 148) = 148
15911 old_mmap(0xbe5c2000, 253952, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xbe5c2000
15911 mprotect(0xbe5c2000, 4096, PROT_NONE) = 0
15911 clone(child_stack=0xbe5ffbf8,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|0x21) = 16036
16036 getpid() = 16036
16036 rt_sigprocmask(SIG_SETMASK, [HUP INT PIPE TERM 32], NULL, 8) = 0
16036 sched_setscheduler(0x3ea4, 0, 0xbe5ffd28) = 0
16036 rt_sigprocmask(SIG_SETMASK, NULL, [HUP INT PIPE TERM 32], 8) = 0
16036 rt_sigsuspend([HUP INT PIPE TERM] unfinished ...
15911 kill(16018, SIGRT_0) = 0
15911 poll( unfinished ...
16036 --- SIGRT_0 (Real-time signal 0) ---
15911 ... poll resumed [{fd=3, events=POLLIN}], 1, 2000) = -1 EINTR
(Interrupted system call)
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 getppid() = 15908
15911 wait4(-1, [WIFEXITED(s) WEXITSTATUS(s) == 0],
WNOHANG|__WCLONE, NULL) = 16036
15911 munmap(0xbe5c2000, 253952)= 0
15911 wait4(-1, 0x8149758, WNOHANG|__WCLONE, NULL) = 0
15911 poll([{fd=3, events=POLLIN}], 1, 2000) = -1 EINTR (Interrupted
system call)
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 getppid() = 15908
15911 wait4(-1, [WIFSIGNALED(s) WTERMSIG(s) == SIGKILL],
WNOHANG|__WCLONE, NULL) = 16018
15911 munmap(0xbedc2000, 253952)= 0
15911 kill(16022, SIGKILL) = 0
16022 ... select resumed )= ? ERESTARTNOHAND (To be restarted)
15911 kill(16021, SIGKILL) = 0
15911 kill(16019, SIGKILL) = 0
15911 kill(16017, SIGKILL unfinished ...
16022 +++ killed by SIGKILL +++
15911 ... kill resumed ) = 0
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 kill(16016, SIGKILL) = 0
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 kill(16015, SIGKILL) = 0
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 kill(15913, SIGKILL) = 0
15911 kill(15912, SIGKILL unfinished ...
15912 ... select resumed )= ? ERESTARTNOHAND (To be restarted)
15911 ... kill resumed ) = 0
15912 +++ killed by SIGKILL +++
15911 kill(15908, SIGKILL) = 0
15911 --- SIGRT_1 (Real-time signal 1) ---
15911 sigreturn() = ? (mask now ~[TRAP KILL STOP])
15911 _exit(0)
