Re: In-house authentication & authorization -- WEB400

Subject: Re: In-house authentication & authorization
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Fri, 30 Dec 2016 14:34:42 -0700
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Job start is an expensive operation. How do you maintain an acceptable
response time, or do your menu clicks just take a very long time. Some web
sites do, I am just wondering.

Job startup plus displaying an initial screen consumes about 20
milliseconds of CPU time. Even with the latency of the Internet, the
response is often sub-second.

After initial startup, subsequent requests typically consume 1 to 5
milliseconds of CPU time. Requests like generating PDF documents require
more time.

This architecture is supporting up to 50 million requests for dynamic
content per day in a production environment on a single IBM i server.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: In-house authentication & authorization , Henrik Rützou

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.