Re: [AOLSERVER] Emacs indents for tcl and C
Well I'm older, and still frightened of putting any characters I can't 'see' in source code. Mind you what really surprises me is that I've *never* met anyone who prefers tabs before...? Quite an eye opener thi ;o) Dossy wrote: [EMAIL PROTECTED]"> On 2002.11.12, Peter M. Jansson <[EMAIL PROTECTED]> wrote: I'm sure Dossy will join the prevailing standard, even though it'sdifferent from his opinion. Surely. I really don't care either way - it's just a trivialconfiguration of my .vimrc. This document: http://www.jwz.org/doc/tabs-vs-spaces.htmlIncludes information on how to set up emacs and vim (vi and nvi users likeme are out-of-luck) to use spaces. I wish Jamie's thinking wasn't so flawed. Let me summarize what hesays:"The holy war surrounding tabs vs. spaces is all about the fact thatsome people want to expand tabs to 2 spaces, some to 4, some to someother level of indentation. Therefore, to end the holy war, weshould stop using tabs and only use spaces and all hold hands andsing koombaya as we agree to all concede our personal preferenes andadopt the preferences of the persons with authority."I can't believe someone as smart as Jamie really said that. As I keepsaying, the /true/ solution is to only use hard tabs (ASCII 0x09) andlet each individual person dictate how it gets displayed. No more holywar, that way.The holy war comes from people who /use/ spaces to indent. It's alltheir fault. It's because of them -- especially when they all usedifferent number of spaces to indent with -- that cau se the holy war.If they'd all just use tabs, then /everyone/ could be pleased so long aseveryone learns how to properly configure their own personal editor ofchoice.Getting everyone to untabify and agree on a specific indentation levelis taking the "you will do it my way and like it" attitude, which isn'tvery nice. Tabifying everything says "you can view the code as youlike, I can view the code as I like, and in the end when we exchangecode between us, it'll display the way we individually prefer." There'sno more holy war, then. The only holy war left is to get everyone tostop using spaces and varying numbers of them. I really think this issue can turn in to a big distraction when we have somuch else to do. You're right. So, lets just drop 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 ownfolly -- then you can let go and quickly move on." (p. 70). -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] Emacs indents for tcl and C
Ah, but again you're just talking about your situation. And I have to say you're wrong. Reading code is what its all about after all. Think about it, its how 'readable' some code is that the standards try to push. By adopting *one* way a formatting code for *reading* you allow everyone to sing off the same hymn sheet, it therefore makes sense to adop that *writing* style yourself. If you want to deviate form that for your own personal use then I'd suggest the owness is on you to have tools to allow that, not to expect everyone else to have to adopt things to cope with your requirement. (like tabs) And, if you're like us and you use pair-programming, it becomes doubly critical :o) Plus, Tabs suck! ;o) Cheers Simon Dossy wrote: [EMAIL PROTECTED]"> On 2002.11.12, Simon Millward <[EMAIL PROTECTED]> wrote: Surely you are contradicting yourself? A standard is just that; a commonway of doing something. Right. The whole purpose of a standard is to 'remove' preference and choice. I disagree.It's not to remove preference and choice. It's to reduce or eliminatevariation of the output of the work effort.The process that each individual craft worker uses to produce the workshouldn't be imposed by the standard (unless, that too is critical tothe actual output of the work effort).In other words: I believe a Coding Standard is to ensure that ALL thecode looks like one person wrote it all ... not to enforce one person'spreferences for code formatting on every other person who has to readthe code.I think there's a big difference.-- 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). -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] Emacs indents for tcl and C
I realise I'm being something of a pedant ;o) but.. Surely you are contradicting yourself? A standard is just that; a common way of doing something. The whole purpose of a standard is to 'remove' preference and choice. So unfortunately if you want to standardize you need to do everything the same way. i.e. if your editing files looking at them with long indents (or re-arranged formatting based on clever display scripts) then your actually not working to standard. 'Here's t'spaces' Simon Dossy wrote: [EMAIL PROTECTED]"> On 2002.11.11, Peter M. Jansson <[EMAIL PROTECTED]> wrote: Indentation, like beauty, is in the eye of the beholder (which, Ithink, was part of your point about the flexibility of using tabsrather than spaces). Exactly my point. Using spaces for indentation makes indenting anauthor-only choice. Using tabs makes indentation a reader-specificchoice.When it comes to code-readability, it should be easy to format the codethat's easiest for the reader to read. For poorly formatted code (thatwhich uses spaces isntead of tabs) I can easily whack ":1^M=G" in vimand have it re-indent everything for me the way I like. It's just apity that if the code needs to be shared, I have to go make editsagainst the original, un-reformatted file.Anyway, it's all a matter of preference and the decision is entirelyarbitrary.-- 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). -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] HTTP 1.1 Pipelining.
Hmm, I haven't looked at the existing (pre 1.1) functionality in much detail, so I can't really comment. I might get chance of the next day or two, but can anyone else save me the trouble and confirm whether these things are functionally equivalent? Andrew Piskorski wrote: [EMAIL PROTECTED]"> On Mon, Nov 11, 2002 at 07:25:20AM +0000, Simon Millward wrote: PS/ I beleive pipelining offers significant efficiency improvements forSSL connections, i.e. its allows these connections to stay alive,removing a significant per-request overhead. This is very salient in I'm all for HTTP 1.1 support as well, but doesn't AOLserver alreadysupport "pipelineing" in the form of the pre-1.1 "keepalive" feature?What's the difference between the two?--Andrew Piskorski <[EMAIL PROTECTED]>http://www.piskorski.com. -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] HTTP 1.1 Pipelining.
I guess also, functionality aside, its getting more important to be 1.1 compliant to satisfy corporate requirements/policies. i.e. one of our customers (quite a major one) insists on 1.1. compliance for any web servers on their intranet. Therefore usefulness aside, 1.1. is starting to become barrier to adoption. I'd certainly be interested in getting involved in acheiving 1.1. PS/ I beleive pipelining offers significant efficiency improvements for SSL connections, i.e. its allows these connections to stay alive, removing a significant per-request overhead. This is very salient in high throughput enviroments such as SMS (GSM text message) handling where the overhead vs the size of an SMS interaction is proportionally significant. Simon Nathan Folkman wrote: [EMAIL PROTECTED]"> In a message dated 11/8/02 10:20:39 AM, [EMAIL PROTECTED] writes: I have a question regarding the latest 3.5.0 release of AolServer. Does this version support HTTP 1.1, and more specifically HTTP 1.1 pipelining? If not, is this planned for the version 4? HTTP 1.1 is not currently supported, and so far there are no plans for adding support for it to the 4.0 version. To be honest it's been a while since I've looked at the 1.1 spec - what's it all about, and what benefits would there be if we were to support it? Would we need to support all of it, or are there particular parts, such as the pipelining you mention, which would be more beneficial then others? - n -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] alloc: invalid block errors
You might be interested in taking a look at the automated testing package that now comes as part of the openACS 4.5/6 core. its actually a framework for organising, deploying and state-setting fo indepenent auto tests (much akin to XP style approach to testing). Although not the same as what your describing, again there is some crossover,and perhaps its another cross-community opportunity. On Tuesday, November 5, 2002, at 08:21 pm, Scott S. Goodwin wrote: 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 release the framework as soon as it is fully functional for community review and comment. Some features: It compiles all source code, configures all software, and run all tests in a fully automated way, all without being root. Don't let this stop you from writing manual or automated tests -- it should be fairly straightforward to migrate that code into the framework. /s. -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Nathan Folkman Sent: Tuesday, November 05, 2002 1:57 PM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] alloc: invalid block errors 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 of nstelemetry.adp and see if anything funny is happening. -- Dossy Perhaps these test scripts could form the foundation of a generic test suite. I know Scott has been thinking a lot about this. - n
Re: [AOLSERVER] Input data verification
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 the function of much of what goes on in OpenACS's request broker is certainly something that might have a place both in the OpenACS community and the AOLServer one in the wider sense. Possibly not everything is there/done/correct, but my thinking is that surely there may be an opportunity to combine a degree of effort/common interest and possibly consider something that neither is 'dependent on' but both could use? 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. Cheers Simon On Tuesday, November 5, 2002, at 05:10 pm, Daniël Mantione wrote: On Tue, 5 Nov 2002, Simon Millward wrote: I'm surprised you say that, unless I'm missing what your trying to achieve. I just checked again and I did found indeed validation code, so sorry about the my false claims, but the are many cases where it is omitted. For example take admin/bboard/administer.tcl, the variable topic_id is never checked if it is a proper integer. Also, the checking done in check_for_form_variable_naughtiness isn't a proper library, these are just OpenACS specific checks. Daniël
Re: [AOLSERVER] Input data verification
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 offers a really simple way to create forms ina single tcl file, that can be defined as widget types, each conforming to a data standard, furthermore each widget can be customised to have further, bespoke validation applied and so on. I suspect that lack of documentation (hey ho, here I go again ;o), and also a lack of good exemplar code and practices in some packages has more to do with it. However,we may be discussing a different kind of issue here? I am understanding correctly? The introduction of a request processor/filter that might offer the chance to peform such validation is what your after? Cheers Simon Daniël Mantione wrote: [EMAIL PROTECTED]"> On Tue, 5 Nov 2002, Simon Millward wrote: This sounds like your trying to create something very like what we havein the OpenACS i.e. the forms API and ad_page_contract. Both of whichprovide extensive and well organised facilites for doing this.Much of what goes on in the OpenACS' request broker is not databasespecific or dependent, and for that matter isn't all that dependent onthe OpenACS datamodel in general.I'm wondering whether there's a case emerging here for creating theOpenACS request processor as an extension to AOLServer (rather than as acomponent of OpenACS) Hmmm. At least OpenACS does not use it itself very well, I've yet to seean example of a page that does verify it's input data...But ok, we should take a look at it then.Daniël. -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] Input data verification
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 dependent, and for that matter isn't all that dependent on the OpenACS
datamodel in general.
I'm wondering whether there's a case emerging here for creating the OpenACS
request processor as an extension to AOLServer (rather than as a component
of OpenACS)
Thoughts?
Patrick Spence wrote:
000801c2845e$1a0431f0$6a7ba8c0@ERIS">
why not the tcl command "string"like: string is integer $string:) http://tcl.activestate.com/man/tcl8.4/TclCmd/string.htm-- Patrick Spence www.RandomRamblings.com www.Ariven.com- Original Message -From: "Daniël Mantione" <[EMAIL PROTECTED]>To: <[EMAIL PROTECTED]>Sent: Monday, November 04, 2002 2:41 PMSubject: [AOLSERVER] Input data verification
Hello,You have propably all build a simple a html form and ascript that processes the form. Now how do you verify your input data?For example, you want the user to enter a number. How do you verify on theserver side that someone indeed sent a number?Usually I use the scan command, i.e.:set r [ns_conn form]set variabletxt [ns_set iget $r variable]if {[scan %d $variabletxt variable] == 0} then {ns_returnnotfoundreturn -code return} else {.}Now this is quite a lot of code for such a simple check and you write itin each form again. I got a bit bored and wrote a library for it. Now itis much easier, at the start of a script I just do:bind_form_vars {mode req num} {actionurl req} {tabledef req} {index num}
{action}
What does this do?- A form variable "mode" is assigned to the variable "mode". The variable is required ("req") and it must be numeric ("num").- The form variable "actionurl" is assign to the variable "actionurl" and it is required.- The same for "tabledef".- "index" is not required, if it is not present the variable "index" will be set to {}, but if it is present it should be numeric- "action" is not requiredNow, since it is a very basic task that allmost every AOLserver user hasto do, is it perhaps an idea to make such a library part of the standardAOLserver distribution?Daniël
.
--
Simon Millward
Director
OpenMSG Limited
+44 (0) 7818 045 801
Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] Call for AOLserver Core Team Nominees
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. I'm sure you'd agree, although I don't know who from the community would be able to take it on. Simon Nathan Folkman wrote: [EMAIL PROTECTED]"> We would like to establish an AOLserver core team made up of members from both here at AOL and the Open Source Community. The core team's main responsibility will be to lead the future direction of the AOLserver Open Source project, working to balance the internal requirements here at AOL with the requirements of the community at large. We've decided to adopt the core team principles currently in use by the Tcl core team - it seems to have worked well for them, and seems to also be a good fit for the AOLserver project. There will probably be a few slight modifications made, but essentially the core team will function as described by the following: http://www.scriptics.com/cgi-bin/tct/tip/0.html If you are interested in becoming a member of the AOLserver core team, please send me ([EMAIL PROTECTED]) an email with a brief paragraph or two describing your qualifications, and why you think you would be a good candidate. We will then post the names and descriptions and allow everyone to vote for the top three. Please let me know if there are any questions. Thanks! - Nathan -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] aolserver doesent listen for connections [Please help!]
Perhaps something else is already using that port? Psycho Tux wrote: Hi all, please help me, please share your knowledge with me! I started nsd whit the command ./nsd -u nsadmin -g nsadmin -t config, then i had these errors in my log [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: nsmain: AOLserver/3.5.0 starting [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: nsmain: security info: uid=501, euid=501, gid=501, egid=501 [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: nsmain: max files: FD_SETSIZE = 1024, rl_cur = 102 4, rl_max = 1024 [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: adp: mapped /*.adp [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nssock. so' [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nslog.s o' [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: nslog: opened '/usr/local/aolserver/bin/servers/se rver1/modules/nslog/access.log' [18/Oct/2002:17:27:51][1480.1024][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nscp.so ' [18/Oct/2002:17:27:51][1480.1024][-main-] Error: nscp: could not listen on 127.0.0.1: [18/Oct/2002:17:27:51][1480.1024][-main-] Error: modload: failed to load '/usr/local/aolserver/bin/n scp.so': 'Ns_ModuleInit' returned -1 [18/Oct/2002:17:27:51][1480.1024][-main-] Fatal: modload: failed to load module '/usr/local/aolserve r/bin/nscp.so' he doesent listen on a unpriviledged port for web connection, i become a connection refused when I try with telnet. __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com . -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] AOLserver and Red Hat 8
I can't comment on Mandrake 9 but traditionally, at the kernel level, Mandrake and RedHat have been quite similar (thats why we use it). The only major difference I've ever really found is that the folks at Mandrake seem to be a bit more switched on, and their distributions are a quality level higher (enough of the Mandrake pitch ;).. As Mandrake is also very fond of claiming they are 100% compatible with RedHat this would lead me to suspect that what applies for one also goes for the other This has tweaked my interest though, so if anyone can provide a definitive answer I'd also like to know Kris, are these new developments RedHat claims, or is this something you've personally verified? Not that I'd *ever* suggest the RedHat folks might claim something thats not quite true ;) Simon Kriston Rehberg wrote: > No, I don't have any idea how or if any of this applies to Mandrake 9. > > Kris > > > [EMAIL PROTECTED] wrote: > >> Kris >> >> Do you (or anyone) know if these multithreaded benefits are spcific to >> Redhat or some aspect of the kernel they are using. I've just downloaded >> Mandrake 9.0 which is using the 2.4.19 kernel and wondered if these >> changes would be seen here (I'll have a dig around myself but thought >> I'd ask in case the answers already known). >> >> Thanks >> >>Steve >> >> On Tue, 2002-10-01 at 05:00, Automatic digest processor wrote: >> >> >> >>> From: Kriston Rehberg <[EMAIL PROTECTED]> >>> Subject: AOLserver and Red Hat 8 >>> Date: 30 Sep 2002 13:55:29 -0400 >>> >>> Hi! With today's release of Red Hat 8.0 there are significantly >>> excellent changes to Red Hat to make life with multithreaded programs, >>> like AOLserver, more convenient. >>> >>> 1) gcc-3.2 is used exclusively throughout Red Hat 8.0. This means that >>> C89, C99, C++, ANSI C++, and friends will work together in harmony as >>> AOLserver shared objects. Please note that there is an >>> inconsistency in >>> the Red Hat 8.0 release notes that claims that the C++ ABI will change >>> in future releaes, but this directly contradicts the actual GCC 3.2 >>> release notes that state clearly that the C++ ABI will not change in >>> future releases. If you're a C++ head be sure to watch out for this >>> but >>> it's probably as easy as keeping your code easy for other people to >>> recompile. >>> >>> 2) Multithreaded program support is getting better and better! The top >>> and ps commands now only display the main (initial) thread of >>> thread-aware processes. To show all threads, use the command ps -m or >>> type H in top. >>> >>> 3) gdb seems to know what it's doing with multithreaded programs and >>> core dumps--I think the jury is still out on this one. >>> >>> 4) The version of Tcl does not have thread support enabled so AOLserver >>> 3.5 users will need to build their own copy of Tcl with >>> "--enable-threads --enable-shared". At runtime, AOLserver at this time >>> does not "detect" that a proper version of Tcl with threads is >>> installed >>> but it's likely we can do this in a future release for all systems. >>> >>> 5) Long ago the default file descriptor limit on Linux was made >>> configurable even if you don't have a 64-bit system. The default Linux >>> installaion has about three zillion times more file descriptors than >>> even Solaris 9. >>> >>> 6) ns_sendmail will work as long as you use "localhost" or "127.0.0.1" >>> as your smtphost. Red Hat 8 only listens on localhost for security >>> reasons. >>> >>> 7) OpenSSL should be rebuilt according to the documentation that comes >>> with nsopenssl, otherwise nsopenssl will not recognize it. >>> >>> >>> That's all I can think of right now. In the meantime, download Red Hat >>> 8.0 and tell us what you think! >>> >>> Kris >>> >>> >>> >>> >>> >> >> >> >> > > . > -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] [ aolserver-Support Requests-608229 ] Cant I use port 80?
You need to run aolserver as root to use port 80. Ms. Source Forge wrote: >Support Requests item #608229, was opened at 2002-09-12 15:56 >You can respond by visiting: >https://sourceforge.net/tracker/?func=detail&atid=203152&aid=608229&group_id=3152 > >Category: Configuration: First-Time Startup >Group: aolserver4_0 >Status: Open >Resolution: None >Priority: 5 >Submitted By: Ho-seung Ahn (saaakan) >Assigned to: Nobody/Anonymous (nobody) >Summary: Cant I use port 80? > >Initial Comment: > I built and Installed Aolsever 4.0 > > But It cant operate using port 80. I'm using my workstation in > >Firewall. This made only use port 80. > > But only port 80 isn't listen to nssock. > >< Error message > > >nssock:fail to listen XXX.XXX.XXX.XXX:80 permission denied > > > > > What can I do for this status? > > >-- > >>Comment By: Ho-seung Ahn (saaakan) >> >Date: 2002-09-12 16:11 > >Message: >Logged In: YES >user_id=610030 > >I'm using Sparc Solaris 8. >Compile is well done. >I was run like this as root. >bin/nsd -ft sample-config.tcl -u saaakan -g root > >If SERVER_PORT make 8000, 8001 or 81 then well work. > >But using 80 make this error. > > > > >-- > >Comment By: Andrew Piskorski (apiskors) >Date: 2002-09-12 16:01 > >Message: >Logged In: YES >user_id=43168 > >You need to give more information. How did you start >AOLserver? Give the command line you used, for instance. > >Are you starting AOLserver as root? You must, as only root >is allowed to listen on port 80. > > >-- > >You can respond by visiting: >https://sourceforge.net/tracker/?func=detail&atid=203152&aid=608229&group_id=3152 > >. > -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] OT: gearing for speed....
Yes ;) jerome wrote: >would there be a difference between an http post compared to an https post in >terms of speed? > >. > -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] pushing aolserver to its limit..
Oh, I should point out that the app. I'm talking about has of course been designed with that level of performance in mind, so there's a good deal of optimisation in the app code itself, but the premise is reasonable enough Simon Millward wrote: > Hi Jerome, > > I have no idea what your hardware set up is, which makes it difficult to > comment. > > In my experiences AOLServer can cater for this comfortably, with the > right environment. Perhaps the most noticable (and simplest) way of > imporving AOLServer performance is more memory > > Having said that you can try uping the number of threads and database > pool connections.. > > You might alos try running more than one AOLServer, again depending on > the kind of hardware you have. > > To give you and idea, on a simple Celeron 1.3GHz with ~300Mb and a > single 10,000rpm disk we can comfortably get about 10-15 per second, and > these are transactions running through OpenACS as well (I.e. Postgres > plus request processor and so on...). And this is on a box that has not > been particularly finely tuned > > Regards > Simon > > jerome wrote: > >> how can i maximize aolserver's performance..?? >> >> based on the current traffic we are receiving 20-30 transactions >> request/sec... >> >> can aolserver cater such request using all available hardware resources? >> >> some are saying that our bottleneck is aolserver because it cant process >> those transactions are there ways to tweak aolserver to push it >> to its >> limit? (though i AFAIK limits exists only on hardware .. >> >> ehehe >> >> >> TIA >> >> . >> > > -- > Simon Millward > Director > OpenMSG Limited > +44 (0) 7818 045 801 > > Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web > http://www.open-msg.net > Any views expressed in this message are those of the individual sender, > except where the sender specifically states them to be the views of > OpenMSG Ltd. > > . > -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] pushing aolserver to its limit..
Hi Jerome, I have no idea what your hardware set up is, which makes it difficult to comment. In my experiences AOLServer can cater for this comfortably, with the right environment. Perhaps the most noticable (and simplest) way of imporving AOLServer performance is more memory Having said that you can try uping the number of threads and database pool connections.. You might alos try running more than one AOLServer, again depending on the kind of hardware you have. To give you and idea, on a simple Celeron 1.3GHz with ~300Mb and a single 10,000rpm disk we can comfortably get about 10-15 per second, and these are transactions running through OpenACS as well (I.e. Postgres plus request processor and so on...). And this is on a box that has not been particularly finely tuned Regards Simon jerome wrote: >how can i maximize aolserver's performance..?? > >based on the current traffic we are receiving 20-30 transactions >request/sec... > >can aolserver cater such request using all available hardware resources? > >some are saying that our bottleneck is aolserver because it cant process >those transactions are there ways to tweak aolserver to push it to its >limit? (though i AFAIK limits exists only on hardware .. > >ehehe > > >TIA > >. > -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] how do i unsubscribe
put UNSUBSCRIBE AOLSERVER in the body of an email to [EMAIL PROTECTED] Or something like that... Simon Millward OpenMSG Limited Tel: +44 (0) 7818 045801 OpenMSG Limited - 4 Hetling Court, Bath, BA1 1SH, England Tel: +44 (0)1225 48-48-05 Fax: +44 (0)1225 31-67-89 Web: http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 28, 2002 1:35 PM Subject: [AOLSERVER] how do i unsubscribe > how do i get off this list. the language is totally foreign to me. >
Re: [AOLSERVER] Failed
Re posted
[AOLSERVER] AOLServer - Text Message software available
Hi folks, Some of you may be interested in integrating AOLServer with a mobile network, and in particular using Text Messages. OpenMSG have recently developed a few extensions to AOLServer that provide queuing, connection management, device drivers and so forth for adding Text Message facilities to you web service. We very much want to pass *anything* we develop back into the community and therefore we've os'ed it all. This was originally developed for use with OpenACS 4.x, but is probably generally useful to other AOLServer users. It provides a serialised set of manageable queues and connections that were originally developed with web-farms and direct operator connections, but it just as usable with a simple GSM modem. It also makes it very easy to run a separate store-and-forward SMS server, allowing multiple services to share a common queuing system. Its made of of (mostly) AOLServer extensions with a simple ACS package if required. Its had a fair bit of testing and been operating for a few months now, so should be reasonably useful. At the moment I'd consider the software in beta and we've not yet had time to publish all our documentation, but some of the more adventurous amongst you may wish to experiment. Obviously its all gpl'ed etc... so your free to use it as you see fit. You can download the software at http://213.107.207.131";>OpenMSG Download Server. (http://213.107.207.131) Hope you find it useful and I always look forward to any feedback. You can either mail me on this list, or better still post up on the OpenACS forums... i read them more frequently. I will put a simple bulletin board up on the site at some point... Warmest regards Simon Millward Director OpenMSG Limited Tel: +44 (0) 7818 045801 OpenMSG Limited - 4 Hetling Court, Bath, BA1 1SH, England Tel: +44 (0)1225 48-48-05 Fax: +44 (0)1225 31-67-89 Web: http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
Re: [AOLSERVER] Procs with 2+ args in ns_register_proc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Too many close braces on the second proc.
Simon Millward
CEO - OpenMSG Limited
www.open-msg.com
(Public Key at www.keyserver.net)
- -Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On
Behalf
Of Gaizka Villate
Sent: 31 May 2001 14:10
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] Procs with 2+ args in ns_register_proc
Is it possible have a proc with more than one argument registered
with
ns_register_proc ?
In the documentation it says it's possible:
(at http://www.aolserver.com/docs/tcldev/tapi-104.htm#3937 ):
ns_register_proc GET /twoargs twoargs fnord
ns_register_proc GET /threeargs threeargs fnord fjord
proc twoargs { conn context { greeble bork } } {
...
} ;
proc threeargs { conn context {greeble bork } { hoover quark } }
{
...
} ;
But when i try it in a session with nscp:
nscp 1> proc threeargs { conn context {greeble bork } { hoover quark}
} } {
return 0
}
b2civi-dev:nscp 2> ns_register_proc GET /threeargs threeargs fnord
fjord
wrong # of args: should be "ns_register_proc ?-noinherit? method url
procName ? args?"
b2civi-dev:nscp 3>
Is there a way to do it?
I've tried passing a list (ns_register_proc GET /threeargs [list
fnord
fjord]) but it hasn't worked.
Thanks a lot for your attention.
- -- Gaizka Villate
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOxZF5rkY0ZOMgcS2EQJotACgioQvdE/sE+q4DW5EJa9vkKHHJfIAoKK4
lP3WLJbRorzACvOYv8IMOySD
=t4C7
-END PGP SIGNATURE-
[AOLSERVER] Good WAP article
Folks, There's a good little intro piece on WAP and AOLServer/ACS at http://www.arsdigita.com/asj/wireless/index.adp worth a squiz if you're not familiar with WAP and mobile stuff... Cheers Simon Millward CEO OpenMSG Ltd. www.open-msg.com
[AOLSERVER] WAP/SMS/I-Mode and AOLServer
Hi, Following my earlier posting, I've had qute a few people ask me about how (and why) we use AOLServer in a mobile context. Apologies if this is not entirely appropriate to the list but as so many people asked We develop services that are 'mobilized' which means that they can be used from a range of interfaces, all essentially communicating with a single server-side application. WAP (or more correctly WML) is essentially a mobile-specific attempt at a markup language not entirely dissimilar to HTML (although there is no direct relation between the two). I'll refrain from offering my personal opinion on WAP/WML, as I'm sure everyone whose had to work with it is already painfully aware of it shortcomings ;-) When a mobile phone issues a WAP based request, it essentially connects to a WAP gateway, more often than not provided by the mobile operator. This gateway acts as a more intelligent node, on behalf of the phone. On good gateways this will handle things like session management, billing interconnectivity, and most importantly from a web development perspective, it maintains 'cookies' on behalf of the phone user. The wap gateway then issues requests to whatever service the user has requested. These services are essentially websites capable of understanding WML. We use AOLServer as our general web server software, but we also extended it so that it can understand (and serve up) WML as well as HTML. This is actually achieved by extending the mime type/headers that AOLServer is able to recognise. This allows us to use a common architecture for delivering both kinds of content, with all the performance benefits of AOLServer. Performance is of course critical for mobile services due to the very low bandwidth available. It goes a little further than this for us. In order to simplify the production of web content for many devices types we also have to employ clever, dynamic content management to serve up the correct content appropriate for the interface, whilst ensuring that concurrent access from any other device is also handled. We therefore also use the excellent ACS and OpenACS to provide a starting point for this. There's actually a good piece on the ArsDigita site about WAP but I don't have the URL to hand unfortunately. We use AOLServer for a number of other mobile based problems as well. Briefly this covers: - We extend AOLServer to act as an agent for interconnecting business systems (such as billing and mediation) by serving up XML content appropriate for Machine-Machine connectivity. - We have a specialised service for the management of SMS traffic. This means we can use text Messages to notify subscribers, or even support very simple session management based on Text Messages, i.e. users can submit commands, queries and responses via SMS. - Support for mediation and micro-billing, v.useful when your dealing with a mobile operator ;-) As an interesting aside, AOLServer is also very competent for serving up content based on i-Mode / cHTML. This is most interesting as we're likely to see the Japanese technology emerging in Europe later this year. Apologies for the length, hope its of some use. Don't hesitate to mail us if you wanted to know anything else (if its not appropriate for the list). Cheers Simon www.open-msg.com
Re: [AOLSERVER] Nokia 2.1 and AOLServer
Hi, Our company actually specialises in mobile service development(WAP/SMS/iMode) using AOLServer along with ACS. If you want to pop your question over we might be able to help. drop it to me or [EMAIL PROTECTED] if you like Cheers Simon Millward CEO OpenMSG Limited www.open-msg.com On Tuesday 15 May 2001 21:34, you wrote: > Is there anybody who works with WAP Technologies and AOL Server. I have a > question regarding the new version of Nokia WAP Browser 2.1?
Re: [AOLSERVER] AOLServer and Mandrake Linux 8.0
This may not be much help, but I can confirm that AOLServer installs fine on Mandrake 8. Apologies if this is glaringly obvious, but you are sure that 63.12.31.202:8000 Is not already assigned or already has something listening on it, i.e. another AOLServer? On Tuesday 15 May 2001 13:47, you wrote: > Hi all, > > This is the very first time I'm attempting to get AOLServer compiled and > going on Linux, after failing miserably using Solaris 8. > > Have just installed a Linux Mandrake 8.0 system, and am attempting to > get AOLServer running on it. Are there any known issues with AOLServer > and Mandrake Linux 8.0? This is a Linux Kernel 2.4.3 SMP machine if > that has any bearing on the situation. > > Have followed this set of instructions : > > a) Uncompressed the AOLServer 3.3.1 tar.gz archive to a temporary > location > b) Using an everyday, normal user, entered this directory and did > "gmake" (no problems there), then "gmake install", then "gmake > install-tests" > c) Created the nsadmin group, created the nsadmin user, having it's > default group also be nsadmin > d) Did chown -Rh nsadmin.nsadmin /usr/local/aolserver > e) su - nsadmin > f) Entered /usr/local/aolserver and copied sample-config.tcl to > config.tcl > > g) (Here's the problem) Attempted to start AOLServer using : > > ../bin/nsd -ft ./config.tcl > > A bunch of foreground startup messages, including these 4 lines : > > [15/May/2001:23:42:24][23259.1024][-main-] Error: nssock: failed to > listen on 63.12.31.202:8000: Cannot assign requested address > [15/May/2001:23:42:24][23259.3076][-nssock-] Notice: nssock: starting > [15/May/2001:23:42:24][23259.3076][-nssock-] Notice: nssock: accepting > connections > [15/May/2001:23:42:24][23259.3076][-nssock-] Notice: exiting > > Anyone have any ideas to solve this and get AOLServer working properly? > > :-) > > Regards and best wishes, > > Justin Clift > > -- > "My grandfather once told me that there are two kinds of people: those > who work and those who take the credit. He told me to try to be in the > first group; there was less competition there." > - Indira Gandhi
