Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Disappearing API docs Date: Sat, 30 Jul 2016 22:33:08 -0400 Organization: Aioe.org NNTP Server Lines: 31 Message-ID: References: <4dvsobh2bbgkq66caohursk91t8bn9iuij@4ax.com> <27115dc3-85aa-4305-99bd-fdfdb28f390a@googlegroups.com> <859110c7-ef6c-421d-8d26-69020e21d094@googlegroups.com> NNTP-Posting-Host: 7SK6yTFfqwlIPNBLl3l7Qg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:35154 On 7/24/2016 12:45 AM, Gene Wirchenko wrote: > On Fri, 22 Jul 2016 19:29:02 -0400, Arne Vajhøj > wrote: >> #People typing in URL's manually are supposed to know that >> #while protocol and hostnames are not case sensitive then >> #the other parts of URL's may be. > > Are they? When do most people get told this? Those people can either do it the easy way and read about it or the hard way and notice that sometimes it does not work and figure out why. > And even if they > know this, who knows what an individual Website does? It does not matter. Assuming that URL's are case sensitive will always work. > For example, Wikipedia appears to not care about the case of the > first letter of each word but does care about the case of the other > letters. Wikipedia uses MySQL and ElasticSearch, which must have way more advanced match options than a standard web server and file system provides. Arne