that's perfectly fine, but trouble comes into play if there are say thousands of files in a directory, and/or a network mount is in use. The problem becomes one of performance. A better trick would be something like, for the file "letter.txt", look for files with "L" and/or "l" as the first char, then "E" and/or "e" as the second, and so on and construct a list. Then present a dialog like you mention if necessary.
I suspect you're about to start college, given your anticipation of learning C/C++. Your BASIC experience will be VERY advantageous to you. While others struggle with the concept of a variable or a for loop, you'll (hopefully) be smooth sailing to an easy A:-)
my personal opinions just changed a little, though it's a somewhat easy fix. Seems there's no standard filename extention to C++ source files. Another post says that one extension is ".C" (some more are cc, CC, cxx, cpp, and probably many others). C source files, OTOH, just use ".c". So unfortunately for me, if I had any.C files lying around, I'd be screwed because gcc uses extensions to identify what's about to be compiled.
If there were to be a case insensitive fs developed, then gcc would have to be modified to recognize.c files as.C and vice/versa, and all the.C files would have to be converted to something else.
IMO, I think things would be easier for the masses if the idea were put in place, but converting to it is certainly without it's glitches. It's making me wonder how Apple's doing it in OSX, as there most likely are.C files in the code somewhere.
yeah, i know. i mentioned in another post one that, for filename "letter.txt", you could look for "L" or "l", then "E" or "e", and so on. For cases where the directory contains a LOT of files (think large real-world production systems), that would actually be much faster and take less computation than having the OS generate a list and then convert them all to a common case.
This all still leaves one problem -- person asks for letter.txt. Does the program load up Letter.txt, or LETTER.TXT?? Two ways to solve that - (1) ask user, or (2) make case-insensitive filenames a mandatory part of the filesystem.
I personally opt for #2, as there will be people out there who wont understand #1.
apache could be considered a user-level program. most people wont know they're using it. if you offer space to regular people on a linux or other unix box for static webpages (ie, the ~username/public_html directory), then apache becomes user level, and the user doesnt know it's being used.
Having case-insensitive filenames becomes a serious thing to consider, as you dont want tech support flooded with people who uploaded a file from their windows-based ftp clients and then cant find it in a browser because they werent using proper capitilization. Windows (by default) displays filenames as "Letter" with notepad icon, whether it be LETTER.TXT, Letter.TXT, letter.txt, etc.
Hence, such a system would be FAR better off having the case insensitivity be implemented at filesystem level.
as for taking a list of filenames and then making them all the same case, then comparing, what if a network mount were in use? Or there were thousands of files (many real-world production systems have that many) in a directory? Or both? Is it really worth searching through all that and/or have all that bandwidth get sucked up when the filesystem can do it all for you?
You may wish to know that Mac OSX has case insensitive filenames in the default filesystem, for the purpose of making things easier for the masses.
ok, you're probably right about the code size required. but what about how fast it executes? If someone asks for letters.txt, and it isnt found, it means checking for Letters.txt, and so on. Each iteration takes TIME. Worst case scenario is that letters.txt does not exist in any form of capitilization, and the end result is that the file is then not found.
As an example -- If Apache were to implement case-insensitive filenames, one could easily DoS a box by sending it LONG filenames (on the order of thousands of letters) that dont exist. The DoS comes into play because the httpd process spends a rediculous amount of time figuring out where a requested file is, only to return a 404 in the end. If someone were to take this and make a DDoS out of it, no one would be able to use the machine because of all the CPU time would be dedicated to resolving those bogus filenames. This would be where implementing it in the filesystem makes life much easier.
There are probably some faster algorithms, like seeing if any files start with "L" or "l", then second letter "E" or "e," but again, it adds unnecessary code to numerous apps.
think about the complexity of that. If "letter.txt" was not found, that means searching for Letter.txt, lEtter.txt, LEtter.txt, leTter.txt, and so forth. Imagine being handed a very long filename. This also bloats every app on the face of the globe, eating away disk space and processor time just for each file.
Trust me, it's far easier to imlement such an idea in the filesystem.
Apple OSX is already case-insensitive in terms of filenames, probably for the reason mentioned. MS Windows/DOS have probably all done that for the exact same reason as well.
Of course, in OSX this did cause a security hole in Apache, but it was small, required a specific setup, and was easily fixed.
I wouldnt be surprised if people in his profession get caught in that situation often. For example, if on a flight from San Francisco to Miami, bad weather in Miami redirects him to another location for a night, New Orleans for instance, then the research for New Orleans has not been done. Sure, he could phone a friend, but that may disturb him and he doesnt want to do that. The airport may have restaurant magazines for sale, but at the inflated prices, it may not be worth it.
Of course, he could always just hit a McDonalds:-)
there are states that do that. NY is the only one I know of, and chances are good there are others.
I typically drive from South Jersey to the DC area, and every toll has EZPass installed, so I can whiz right through, and I've never gotten anything unusual in the mail relating to going from the Deleware Memorial Bridge from NJ to the I-95 toll exiting DE. Limit through this stretch is 55, but everyone goes 65+.
not quite. there were 19 comments that were score 5, and 10 that were score 4. They only send 10 questions to the interviewee. We dont know which questions were actually sent off.
that's exactly the type of stuff the other 9 states are going after, as they recognized such things were gonna happen. Testimony during the recent hearing against MS (by Dell, and some other OEMs, I think) actually illustrated this quite well.
...Ted Williams was a great baseball player for the Boston Red Sox, who died last July. Baseball is a very popular sport in the US and Canada, somewhat like cricket in that you hit a ball and run. The Red Sox are a professional team in Boston, Massachusetts.
He was last guy to finish a season with a better than.400 batting average, meaning more than 40% of his at bats were hits that season. A controversy over what to do with his body since has arisen his death, among them cryogenical freezing.
nothing was said about broadcast flags, does this mean there wont be any? Or that it's still under debate? or did the FCC actually say "screw you" to the MPAA?
an NP-complete (NP=non-polynomial) problem is one that can be solved, but takes about 8*age_of_universe time to solve. To get around this, approximation algorithms are used, but these can never give a 100% guarantee of finding the correct solution, nor may provide the same solution if it were to execute on the same data twice.
a polynomial-time problem is one that can be solved within our lifetimes, guarantee 100% accuracy, and can always generate the same solution for the same data.
there's a LOT more to it. The book Intro to Algorithms has a good chapter on the topic of NP-completeness, which will explain the intricate and gory details.
recently my local news had a story about a household that used solar. they actually sell their excess to the electric company, to the tune of something like $300 a month. apparently it paid off the equipment in about two years, and now they just collect as profit!
Slashdot Mirror
Get this --
FreeDOS is GPL'd!!! That's REALLY showin it to MS!!
move the pages to a non-US server! Let's see Verizon try to pull it down now!
if a demo machine bsods, they say "Houston, we have a problem"
that's perfectly fine, but trouble comes into play if there are say thousands of files in a directory, and/or a network mount is in use. The problem becomes one of performance. A better trick would be something like, for the file "letter.txt", look for files with "L" and/or "l" as the first char, then "E" and/or "e" as the second, and so on and construct a list. Then present a dialog like you mention if necessary.
:-)
I suspect you're about to start college, given your anticipation of learning C/C++. Your BASIC experience will be VERY advantageous to you. While others struggle with the concept of a variable or a for loop, you'll (hopefully) be smooth sailing to an easy A
my personal opinions just changed a little, though it's a somewhat easy fix. Seems there's no standard filename extention to C++ source files. Another post says that one extension is ".C" (some more are cc, CC, cxx, cpp, and probably many others). C source files, OTOH, just use ".c". So unfortunately for me, if I had any .C files lying around, I'd be screwed because gcc uses extensions to identify what's about to be compiled.
.c files as .C and vice/versa, and all the .C files would have to be converted to something else.
.C files in the code somewhere.
If there were to be a case insensitive fs developed, then gcc would have to be modified to recognize
IMO, I think things would be easier for the masses if the idea were put in place, but converting to it is certainly without it's glitches. It's making me wonder how Apple's doing it in OSX, as there most likely are
well, Solaris 9 for SPARC can be d'loaded for free (as in beer), so I hope similar treatment for x86 is in store. See http://wwws.sun.com/software/solaris/binaries/get. html
not quite. according to the article on eweek (linked above):
....
On Monday, Sun CEO, Chairman and President Scott McNealy will also unveil a new, general-purpose x86-based server, the Sun LX50,
[emphasis mine]
how much? will it cost regular home users cost of shipping only like past versions?
yeah, i know. i mentioned in another post one that, for filename "letter.txt", you could look for "L" or "l", then "E" or "e", and so on. For cases where the directory contains a LOT of files (think large real-world production systems), that would actually be much faster and take less computation than having the OS generate a list and then convert them all to a common case.
This all still leaves one problem -- person asks for letter.txt. Does the program load up Letter.txt, or LETTER.TXT?? Two ways to solve that - (1) ask user, or (2) make case-insensitive filenames a mandatory part of the filesystem.
I personally opt for #2, as there will be people out there who wont understand #1.
apache could be considered a user-level program. most people wont know they're using it. if you offer space to regular people on a linux or other unix box for static webpages (ie, the ~username/public_html directory), then apache becomes user level, and the user doesnt know it's being used.
Having case-insensitive filenames becomes a serious thing to consider, as you dont want tech support flooded with people who uploaded a file from their windows-based ftp clients and then cant find it in a browser because they werent using proper capitilization. Windows (by default) displays filenames as "Letter" with notepad icon, whether it be LETTER.TXT, Letter.TXT, letter.txt, etc.
Hence, such a system would be FAR better off having the case insensitivity be implemented at filesystem level.
as for taking a list of filenames and then making them all the same case, then comparing, what if a network mount were in use? Or there were thousands of files (many real-world production systems have that many) in a directory? Or both? Is it really worth searching through all that and/or have all that bandwidth get sucked up when the filesystem can do it all for you?
You may wish to know that Mac OSX has case insensitive filenames in the default filesystem, for the purpose of making things easier for the masses.
ok, you're probably right about the code size required. but what about how fast it executes? If someone asks for letters.txt, and it isnt found, it means checking for Letters.txt, and so on. Each iteration takes TIME. Worst case scenario is that letters.txt does not exist in any form of capitilization, and the end result is that the file is then not found.
As an example -- If Apache were to implement case-insensitive filenames, one could easily DoS a box by sending it LONG filenames (on the order of thousands of letters) that dont exist. The DoS comes into play because the httpd process spends a rediculous amount of time figuring out where a requested file is, only to return a 404 in the end. If someone were to take this and make a DDoS out of it, no one would be able to use the machine because of all the CPU time would be dedicated to resolving those bogus filenames. This would be where implementing it in the filesystem makes life much easier.
There are probably some faster algorithms, like seeing if any files start with "L" or "l", then second letter "E" or "e," but again, it adds unnecessary code to numerous apps.
that's actually what Windows does, though Windows can lose track of capitilization if a file gets copied to floppy and back, etc...
ah! i forgot about that. It's been a while since I've touched OSX. Which is the one installed by default?
think about the complexity of that. If "letter.txt" was not found, that means searching for Letter.txt, lEtter.txt, LEtter.txt, leTter.txt, and so forth. Imagine being handed a very long filename. This also bloats every app on the face of the globe, eating away disk space and processor time just for each file.
Trust me, it's far easier to imlement such an idea in the filesystem.
Apple OSX is already case-insensitive in terms of filenames, probably for the reason mentioned. MS Windows/DOS have probably all done that for the exact same reason as well.
Of course, in OSX this did cause a security hole in Apache, but it was small, required a specific setup, and was easily fixed.
I wouldnt be surprised if people in his profession get caught in that situation often. For example, if on a flight from San Francisco to Miami, bad weather in Miami redirects him to another location for a night, New Orleans for instance, then the research for New Orleans has not been done. Sure, he could phone a friend, but that may disturb him and he doesnt want to do that. The airport may have restaurant magazines for sale, but at the inflated prices, it may not be worth it.
:-)
Of course, he could always just hit a McDonalds
there are states that do that. NY is the only one I know of, and chances are good there are others.
I typically drive from South Jersey to the DC area, and every toll has EZPass installed, so I can whiz right through, and I've never gotten anything unusual in the mail relating to going from the Deleware Memorial Bridge from NJ to the I-95 toll exiting DE. Limit through this stretch is 55, but everyone goes 65+.
not quite. there were 19 comments that were score 5, and 10 that were score 4. They only send 10 questions to the interviewee. We dont know which questions were actually sent off.
do you think you could at least post the questions that you sent his way? mayne then we could all get an idea of what trouble might have been caused.
that's exactly the type of stuff the other 9 states are going after, as they recognized such things were gonna happen. Testimony during the recent hearing against MS (by Dell, and some other OEMs, I think) actually illustrated this quite well.
...Ted Williams was a great baseball player for the Boston Red Sox, who died last July. Baseball is a very popular sport in the US and Canada, somewhat like cricket in that you hit a ball and run. The Red Sox are a professional team in Boston, Massachusetts.
.400 batting average, meaning more than 40% of his at bats were hits that season. A controversy over what to do with his body since has arisen his death, among them cryogenical freezing.
He was last guy to finish a season with a better than
nothing was said about broadcast flags, does this mean there wont be any? Or that it's still under debate? or did the FCC actually say "screw you" to the MPAA?
HDTV-compatible sets have been on the market for a few years. Are they changing the HDTV spec enough such that these TV's wont be able to work?
a simple way to think of it:
an NP-complete (NP=non-polynomial) problem is one that can be solved, but takes about 8*age_of_universe time to solve. To get around this, approximation algorithms are used, but these can never give a 100% guarantee of finding the correct solution, nor may provide the same solution if it were to execute on the same data twice.
a polynomial-time problem is one that can be solved within our lifetimes, guarantee 100% accuracy, and can always generate the same solution for the same data.
there's a LOT more to it. The book Intro to Algorithms has a good chapter on the topic of NP-completeness, which will explain the intricate and gory details.
recently my local news had a story about a household that used solar. they actually sell their excess to the electric company, to the tune of something like $300 a month. apparently it paid off the equipment in about two years, and now they just collect as profit!