I'm playing around with the update interval - the data is real-time from the remote
server. I want to eliminate much network traffic and server overhead by calling the
remote server for the data every few seconds, rather than every HTTP request as is now
the case.
Appreciate your comments!
-mark
>>> Joe Sam Shirah <[EMAIL PROTECTED]> 7/12/99 12:22:31 AM >>>
Yep, anything in memory will be at least an order of magnitude faster
than disk access ( yes, cache aside, ) if you have it to spare. Especially
here, when it seems there is no reason to store the data ( always available
from another server. ) Even if you needed to keep the data, not sure why
you would access it every 5 seconds when you know it is updated every 10
seconds.
Joe Sam
-----Original Message-----
From: Rod McChesney <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Sunday, July 11, 1999 7:44 PM
Subject: Re: C or Java?
>How about option 3 of calling server A call from Java and using a
>servlet for the whole process?
>
>Rod McChesney, Korobra
>
>
>Mark Galbreath wrote:
>>
>> Question of speed of delivery.
>>
>> Scenario:
>> I have a remote server A that calls remote server B through the firewall
to retrieve a pipe-delimited string of real-time market quotes. At present
the webserver makes a Perl CGI call to server A to get the data, formats it
into an HTML table, and serves it up on the homepage (www.troweprice.com).
So every HTTP GET request to the webserver spawns a separate process to
fetch and process the quote data.
>>
>> New Design Options (forget CORBA for the moment):
>> 1. Have a cron run the Perl script to write the quote data to a flatfile
every 10 seconds; have a Java servlet read that file every five seconds,
holding the data in memory, and delivering the formatted HTML to the clients
per request by spawning multiple threads.
>>
>> 2. Have a cron run a C version of the script to get the data every 10
seconds and renew an otherwise static HTML page that will be served by the
webserver per every HTTP GET request.
>>
>> Which solution do you think would be the faster? Are there others I am
neglecting?
>>
>> Thanks for the input (pun intended)!
>>
>> -mark
>>
>>
___________________________________________________________________________
>> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
>> of the message "signoff SERVLET-INTEREST".
>>
>> Archives: http://archives.java.sun.com/archives/servlet-interest.html
>> Resources: http://java.sun.com/products/servlet/external-resources.html
>> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
