Thanks for your comments.
The reasoning for this is quite simply because of the hpHosts & mvps Hosts etc files, that contain server IP's/URL's that are no longer valid (my app simply detects and reports their validity). The contents themselves will not be stored unless the user asks my app to do so.
--
Regards
Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk
Keeping it FREE!
"Mark J. McGinty" <mmcginty@spamfromyou.com> wrote in message news:eupwj91XFHA.1240@TK2MSFTNGP14.phx.gbl...[color=blue]
> [I don't understand why my news reader won't prefix the lines from the OP...
> sorry for any confusion... I prefixed the short sections by hand...]
> [color=green][color=darkred]
> >>>>>>>>>>>>>>>>>>>[/color][/color]
> "Steven Burn" <somewhere@in-time.invalid> wrote in message
> news:uTq3LGtXFHA.3540@TK2MSFTNGP15.phx.gbl...
> The application;
>
> Service on my webserver that allows a user to upload their HOSTS file for
> functions to verify the contents are still valid.
>
> [snip]
>
> The problem;
>
> The file can contain anything from 10 lines to 20,000+ lines, each one is
> parsed and passed to the URLExists function. I'm not entirely sure whether
> the problem is due to the content itself, or the number of calls to the
> XMLHTTP object but, a file containing 10,000 lines (the test file) times out
> after around 1,000 lines.
>
> The timeout set for the URLExists function is 5 seconds (the timeout takes
> well over an hour of reading/parsing, to occur), the script timeout is set
> to 5000
> [color=green]
> > I've tried cutting alot of the content of the test file out so it's 206K
> > instead of 1.10MB, but it's still taking forever to process, and then
> > timing
> > out anyway.[/color]
> <<<<<<<<<<<<<<<<<<<
>
>
>
> Are there really boxes out there with HOSTS files anywhere even near that
> long? We're talking %windir%\system32\drivers\etc\HOSTS, yeah? Any time
> I'm even tempted to put more than 25 lines in HOSTS [esp. the same
> entries on more than one PC] I find somewhere reasonably convenient to
> install BIND! Don't like 99.5% of the HOSTS files out there have just one
> line?
>
> 127.0.0.1 localhost
>
> Sorry if all that's beside the point, I'm mostly just curious as to whether
> or not this commonly exists, and if so, why?
>
>
> [color=green][color=darkred]
> >>>>>>>>>>>>>>>>>>>>>[/color]
> > The question;
> >
> > I've found some doc's online that show how to read and parse large files
> > with a ton of content and have applied this to the application in question
> > but for reasons best known to itself, it is still timing out. What I'm
> > wondering is;
> >
> > 1. Would it be best to ditch the application server-side and make it a
> > downloadable application instead?[/color]
> <<<<<<<<<<<<<<<<<<<<<<
>
>
>
> I would think so. You don't really care about the contents, do you? Aren't
> you really only interested in whether or not the file has changed? I can
> see potential value in storing the last confirmed copy off of the local
> machine, to prevent tampering, but wouldn't a CRC be just a valid of a
> check, without all the muss and fuss?
>
> I would also consider setting a file system change hook, and then comparing
> the contents [CRC] to a non-locally stored value just once per session, to
> verify that it was not changed while your app wasn't running. After that,
> you'll know instantly when any other changes are made.
>
> Long story short, the only real value a server-side process can add to this
> paradigm is off-site storage.
>
>
>
> [color=green][color=darkred]
> >>>>>>>>>>>>>>>>>>>>>>>>[/color]
> > It would be easier to work with in VB but thats the reason I didn't
> > want
> > to do it that way (I like a challenge).
> >
> > 2. Would it be viable to split the file into parts once uploaded, and
> > process each part seperately instead of doing it the way I'm currently
> > doing
> > it?.
> >
> > 3. Is there a better alternative that I've simply not thought of?[/color]
> <<<<<<<<<<<<<<<<<<<<<<<<<<
>
>
>
> If you really have a good reason to parse and store the contents
> entry-for-entry, then I'd store them in a database and leverage that
> technology, that's by far the easiest way to make this kind of thing scale.
>
>
> -Mark
>
>
>
>
> [/color]
