Thorpe Mayes | 15 Dec 23:34

[AOLSERVER] ns_httpspost generating an error

Hi,

I am trying to create a listener for PayPal transactions.

When I do this:

set page [ns_httpspost $url $rqset $qsset]

where url = a https url
rqset is empty
qsset is a set of parameters

I get the following error:

invalid command name "ns_openssl_sockopen"
   while executing
"ns_openssl_sockopen -nonblock $host $port"
   (procedure "ns_httpsopen" line 42)
   invoked from within
"ns_httpsopen POST $url $rqset $timeout $querystring"
   (procedure "ns_httpspost" line 124)
   invoked from within
"ns_httpspost $url $rqset $qsset"

I am running aolserver 4.5.0

Thanks,

Thorpe

(Continue reading)

Levy Bajamundi | 14 Dec 10:16
Picon

[AOLSERVER] Get current urls from Nslimits and Nspools?

Hi,

Is there a way to get the current urls being served via ns_pools or ns_limits? We're trying to figure out why our average latency has bumped up since we migrated over from 4.0 to 4.5.1.


Thanks,

Levy

------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits? 
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
_______________________________________________
aolserver-talk mailing list
aolserver-talk <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
Jeff Rogers | 14 Dec 01:03

[AOLSERVER] ns_http

Hey all,

I'm in the process of making some additions to ns_http (especially a 
"waitall" subcommand that waits for any outstanding request to finish; 
useful when you're making a lot of requests) and I got to wondering if 
ns_http would be better as an external module (where it might be more 
flexible to update) or if people prefer it in the core.

Thoughts?

-J

------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits? 
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
_______________________________________________
aolserver-talk mailing list
aolserver-talk <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

Thorpe Mayes | 12 Dec 15:51

[AOLSERVER] How to use ns_limit?

Hi,

How do I implement ns_limits?

Can I enter the following is the config file:

ns_limits set default -maxupload [expr 15 * 1024 * 1024]

or, do I need to do something else?

Thanks, 

Thorpe

Thorpe Mayes
tmayes <at> ecognizant.com

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
_______________________________________________
aolserver-talk mailing list
aolserver-talk <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

John Buckman | 19 Nov 13:17
Favicon
Gravatar

[AOLSERVER] awstats LogFormat= question

Is anyone using awstats with aolserver?

Can you share your LogFormat= line from your awstats.conf file?

LogFormat=4 (the default) works, but doesn't support a number of awstats features.  

I could RTFM and figure out the exact awstats LogFormat= line, but if someone has already done it...

-john

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
aolserver-talk mailing list
aolserver-talk <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

aT | 10 Nov 08:57
Picon

Slow download speed

Hi , 

Over a single internet connection i tried downloading a zip file from Aolserver and from Nginx.  Aolserver was giving me download speed in my particular case 10-15 KB/s  , whereas same file downloaded from Nginx with more than 800 KB/s .

Both Nginx and Aoslerver (4.5.1) are hosted on the same server , same OS , 

Is there any hidden resource limiting in Aolserver 4.5.1 ?

Thanks in advance for any insight , 


-- 

Dossy Shiobara | 27 Oct 06:42
Favicon
Gravatar

AOLserver mailing lists have now moved to SourceForge

Dear AOLserver Community,

On October 17th, AOL has informed us that they will be discontinuing
their LISTSERV service as of November 1st, 2011.  For over 10 years now,
the AOLserver community's email lists have been hosted through this
offering.

Since the AOLserver open source project is currently hosted at
SourceForge, it only seemed fitting to move our mailing lists over to
the Mailman list offering that SourceForge provides.  I have migrated
all current subscribers from LISTSERV to Mailman.

NOTE: You may receive several copies of this email, as I'm sending it to
the new Mailman lists as well as the previous LISTSERV lists, to ensure
that everyone will receive at least copy of this message.

You can manage your mailing list preferences on the following page:

    https://sourceforge.net/mail/?group_id=3152

There are three mailing lists:

    1) AOLserver Announcements

    aolserver-announce <at> lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/aolserver-announce

    This is a low-traffic, announcement-only mailing list.

    2) AOLserver Discussion List

    aolserver-talk <at> lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/aolserver-talk

    This is the general-purpose discussion mailing list for the
AOLserver community.

    3) AOLserver Commit Notifications

    aolserver-commits <at> lists.sourceforge.net
    https://lists.sourceforge.net/mailman/listinfo/aolserver-commits

    This list receives all source code commit notification messages and
is primarily intended for developers who wish to receive these
notifications.

Unfortunately, there doesn't appear to be a way for me to import the
previous LISTSERV archives into the new Mailman setup, so our 10+ years
of past activity won't be accessible through the SourceForge archives.

Fortunately, there are other list archive services out there who have
mirrored our mailing lists, so archives should continue to be available
that way:

    http://www.mail-archive.com/aolserver <at> listserv.aol.com/
    http://www.mail-archive.com/aolserver-announce <at> listserv.aol.com/

    http://news.gmane.org/gmane.comp.web.aolserver

As always, if there are any questions or concerns, please do not
hesitate to contact me or the aolserver-talk list to discuss.

Thanks,

Dossy Shiobara

--

-- 
Dossy Shiobara         |      "He realized the fastest way to change
dossy <at> panoptic.com     |   is to laugh at your own folly -- then you
http://panoptic.com/   |   can let go and quickly move on." (p. 70) 
  * WordPress * jQuery * MySQL * Security * Business Continuity *

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning <at> Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
aolserver-talk mailing list
aolserver-talk <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

Matthew M. Burke | 24 Oct 04:09
Favicon

Discussing AOLserver at the Tcl/Tk conference

Later this week, the 18th Tcl/Tk conference will be held and one of the 
sessions is a panel discussing the different ways to use Tcl to do web 
development.

I have been asked to discuss AOLserver and as I finish up my notes, I 
thought I should check with the folks on this list to see if there's 
anything that you'd recommend I mention.

If I was more organized, I'd post my notes for folks to peruse in 
advance.  But, alas, I'm not...  I will get them posted as soon as I can.

Just to give you a rough idea of my perspective:  I started using 
AOLserver at Ars Digita in the late 90s.  Since then I've used it (in 
conjunction with .LRN) while on the faculty at St. Mary's College to 
support my classes, and have off-and-on used it to run a few, very 
low-traffic, personal sites.

Thanks for your advice/suggestions,

Matt

Dossy Shiobara | 19 Oct 14:25
Favicon

Fwd: AOL Listserv to be Discontinued

Everyone,

It appears that AOL is going to be shutting own its LISTSERV, which
includes several AOLserver mailing lists.

Since there's still activity on this mailing list, I think it would be
worth "moving" to a new list.  SourceForge offers GNU Mailman lists as
part of its project hosting offering.

Does anyone have a strong preference as to where to relocate the lists?
 Any good reasons why they shouldn't move to SourceForge?

I'd like to try and wrap up discussion around this by Wednesday, October
26th, to give us time to actually perform the relocation of the list, if
possible.

Thanks,

Dossy Shiobara

-------- Original Message --------
Subject: 	AOL Listserv to be Discontinued
Date: 	Tue, 18 Oct 2011 00:59:58 +0000
From: 	AOL Listserv Service <AOL.Listserv.Service <at> teamaol.com>
To: 	AOL Listserv Service <AOL.Listserv.Service <at> teamaol.com>

 Dear AOL Listserv Administrator,

You are receiving this email because you have been listed as the
administration for one or more lists hosted by AOL’s listserv service.
We would like to inform you that AOL will be discontinuing the listserv
service on November 1^st , 2011.  If your list is still actively used,
please make arrangements to find another service prior to the shutdown
date and notify your list members of the transition details.  If you are
no longer actively using this service then no other action is required.

If you have any questions, please contact
AOL.Listserv.Service <at> teamaol.com.  Thank you.

--

-- 
Dossy Shiobara         |      "He realized the fastest way to change
dossy <at> panoptic.com     |   is to laugh at your own folly -- then you
http://panoptic.com/   |   can let go and quickly move on." (p. 70)
  * WordPress * jQuery * MySQL * Security * Business Continuity *

Jeff Rogers | 19 Oct 07:45

recent updates

Hey all, me again.

For those of you who don't monitor the commits list I wanted to share a 
few changes I've recently made as well as a few I'm still thinking about.

- implemented native decoding of strings in ns_returnfile.  This allows 
filenames that are not utf-8 to be passed, similar to tcl core functions.

- committed a long-outstanding patch to address a fastpath caching bug 
where incorrect file content could be delivered in a system when inodes 
are rapidly being reused.  Added a new config option "cacheminage" to 
control this behavior.

- implemented a suggestion to re-run pre-auth and post-auth filters on 
internal redirects.  As this could break assumptions in unusual 
situations, there is a config option "filterredirect" to disable it. 
Among other things, this addresses an issue in openacs that made it 
complicated to handle 404 errors.  Also fixed a server crash when there 
is an error in the configured error page.

- added flags to insert a filter at the beginning of the list of 
registered filters instead of only at the end, and to order filters by 
priority.

- exposed the gzip flag to tcl scripts (ns_conn gzip)

- added another new filter, "pre-write" which runs after content has 
been returned but before it has been sent over the network.  To make 
this useful, there is a new method to ns_conn to examine and set the 
response content that is about to be sent.  This could be useful for 
implementing something like apache's mod_pagespeed, which rewrites 
content to do things like merge javascript and css files to reduce 
external requests, or just strip extraneous whitespace from a page.

- added a tuning knob "maxaccept" to let the driver accept more than one 
connection per spin.  The SF RFE for this referenced a paper that found 
this type of change could improve performance and reduce dropped 
connections under load;  I unfortunately don't have a network capable of 
simulating enough load to stress this so I cannot claim any measured 
improvement.

I also have a few other ideas I haven't gotten around to adding (or even 
necessarily thinking through completely) yet:

- removing encoding and gzip compression from the normal response 
writing codepath (Ns_ConnFlush) and making them into pre-write filters.

- adding an api to name C-coded filters and handler procs such that they 
could be used by the tcl ns_register_filter/ns_register_proc commands. 
This could eliminate a few special-purpose commands that do this same 
thing for particular operations (ns_register_fastpath and 
ns_register_filter_shortcut).

- add support for chunked encoding for requests, digest authentication, 
and Expect: 100-continue.  I've heard that these are already supported 
in NaviServer, so this may be a fairly simple cut&paste enhancement.

- replace c-coded versions of many file operations with equivalent 
tcl-coded versions.  Many of these functions (e.g., ns_mkdir, ns_cp) 
come from before tcl had equivalent functionality, but tcl now has that 
functionality, and it's better (native decoding).

- replace ns_share with tcl version built around nsv, if not eliminating 
it entirely.

- remove other really old code like tclx keylist support.  I honestly 
don't know if this is still being used, perhaps it could be kept around 
in a "nscompat" module along with other things like ns_var and 
ns_share).  I'm a bit reluctant to break compatibility without an easy 
switch to un-break it.

- make content sending event based, by pushing it back to the driver 
thread, a task thread, or a completely new writer thread, rather than 
blocking a conn thread if the content is big and the network is slow. 
There is support for doing this at the tcl level, but it would be nice 
to have it implicitly happen everywhere.

- let queue-waits be set up from a conn thread and the conn re-queued in 
the driver thread.  This would let you do database operations before 
making network calls and still wait for those calls to complete without 
tying up conn threads.  This would mean a rather esoteric coding style 
but I think it would make for a really powerful mashup engine.

Some of these are pretty disruptive (especially the last two), and 
introducing incompatibilities (even ones with an easy off switch) is not 
something to be taken lightly;  does anyone else think a new 4.5.2 
release with the recent bugfixes and non-disruptive new features could 
be done, and then slightly disruptive stuff (i.e., moving c-coded 
commands to tcl) could be targeted at 4.6?

Naturally, I'm also interested in any feedback on anything I've done or 
suggested also.

Cheers,
-J

Thorpe Mayes | 14 Oct 02:21

Unable to install nssolid database driver on aolserver4.5.0

Hi,

I am trying to install the solid database drivers and cannot do it. 

I am running aolserver 4.5.0.

I added the nssolid_3.0 driver. I then added solid-fix.tar, which updated the Makefile file and added the
nssolid.h file to the nssolid directory.

When I run "make" I get this result:

make
gcc -pipe -I/usr/local/solid/solidSDKe352/Linux_glibc2/include -DSOLVER=350 -O2 -Wall
-Wno-implicit-int -fno-strict-aliasing -fPIC  -I/usr/local/aolserver/include
-I/usr/local/include  -DNO_CONST  -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1
-DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1
-DHAVE_PTHREAD_ATFORK=1 -DTCL_THREADS=1 -DPEEK_XCLOSEIM=1 -D_LARGEFILE64_SOURCE=1
-DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_OPEN64=1 -DHAVE_LSEEK64=1
-DHAVE_TYPE_OFF64_T=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1
-DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DUSE_TERMIOS=1
-DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1
-DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_BLKSIZE=1
-DSTDC_HEADERS=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -DHAVE_SYS_IOCTL_H=1 
-DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\"
-DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_TIMEGM=1 -DHAVE_DRAND48=1
-DHAVE_RANDOM=1 -DHAVE_POLL=1 -DHAVE_GETADDRINFO=1 -DHAVE_GETNAMEINFO=1    -c -o nssolid.o nssolid.c
nssolid.c:89: error: expected ‘)’ before ‘*’ token
nssolid.c:90: error: expected ‘)’ before ‘*’ token
nssolid.c:91: error: expected ‘)’ before ‘*’ token
nssolid.c:92: error: expected ‘)’ before ‘*’ token
nssolid.c:93: error: expected ‘)’ before ‘*’ token
nssolid.c:94: error: expected ‘)’ before ‘*’ token
nssolid.c:95: error: expected ‘)’ before ‘*’ token
nssolid.c:96: error: expected ‘)’ before ‘*’ token
nssolid.c:97: error: expected ‘)’ before ‘*’ token
nssolid.c:101: error: expected declaration specifiers or ‘...’ before ‘Ns_DbHandle’
nssolid.c:105: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘odbcProcs’
nssolid.c: In function ‘Ns_DbDriverInit’:
nssolid.c:133: warning: implicit declaration of function ‘Ns_DbRegisterDriver’
nssolid.c:133: error: ‘odbcProcs’ undeclared (first use in this function)
nssolid.c:133: error: (Each undeclared identifier is reported only once
nssolid.c:133: error: for each function it appears in.)
nssolid.c: In function ‘Ns_ODBCShutdown’:
nssolid.c:154: warning: passing argument 2 of ‘ODBCLog’ makes integer from pointer without a cast
nssolid.c:154: error: too many arguments to function ‘ODBCLog’
nssolid.c: At top level:
nssolid.c:182: error: expected ‘)’ before ‘*’ token
nssolid.c:227: error: expected ‘)’ before ‘*’ token
nssolid.c:244: error: expected ‘)’ before ‘*’ token
nssolid.c:291: error: expected ‘)’ before ‘*’ token
nssolid.c:352: error: expected ‘)’ before ‘*’ token
nssolid.c:411: error: expected ‘)’ before ‘*’ token
nssolid.c:417: error: expected ‘)’ before ‘*’ token
nssolid.c:443: error: expected ‘)’ before ‘*’ token
nssolid.c:499: error: expected ‘)’ before ‘*’ token
nssolid.c: In function ‘ODBCCmd’:
nssolid.c:552: error: ‘Ns_DbHandle’ undeclared (first use in this function)
nssolid.c:552: error: ‘handle’ undeclared (first use in this function)
nssolid.c:562: warning: implicit declaration of function ‘Ns_TclDbGetHandle’
nssolid.c:566: warning: implicit declaration of function ‘Ns_DbDriverName’
nssolid.c:566: warning: comparison between pointer and integer
nssolid.c:573: error: too many arguments to function ‘ODBCLog’
nssolid.c:583: error: too many arguments to function ‘ODBCLog’
nssolid.c: At top level:
nssolid.c:617: error: expected declaration specifiers or ‘...’ before ‘Ns_DbHandle’
nssolid.c: In function ‘ODBCLog’:
nssolid.c:633: warning: pointer targets in passing argument 4 of ‘SQLError’ differ in signedness
nssolid.c:633: warning: pointer targets in passing argument 6 of ‘SQLError’ differ in signedness
nssolid.c:638: error: ‘handle’ undeclared (first use in this function)
make: *** [nssolid.o] Error 1

Thanks,

Thorpe

Thorpe Mayes
405.514.9753


Gmane