text:
User talk:PatrickDunfordNZ

Welcome to the Wikipedia
Here are some links I thought useful:

 * Tutorial
 * Help desk
 * Foundation issues
 * Policy Library
 * Utilities
 * Cite your sources
 * Verifiability
 * Wikiquette
 * Civility
 * Conflict resolution
 * Brilliant prose
 * Neutral point of view
 * Pages needing attention
 * Peer review
 * Bad jokes and other deleted nonsense
 * Village pump
 * Boilerplate text
 * IRC channel
 * Mailing lists
 * Current polls

Feel free to ask me anything the links and talk pages don't answer. You can sign your name by typing 4 tildes, like this: ~.

Be Bold!

Sam [Spade] 03:22, 6 Aug 2004 (UTC)

Hi Patrick, Good to have your input on things. Keep it up. One Salient Oversight 04:10, 6 Aug 2004 (UTC)

Hello. When you write a new article on religion, could you add it to the list of religious topics? That alerts some interested readers to its existence. Also, if you find one that is not already listed there (a few weeks ago I found that the article titled Easter was not listed there; I was quite surprised). Michael Hardy

Hello Patrick
We have a few things in common. We both live in Chch, work as computer technicians, contribute to Wikipedia and the newsgroups. However, I am an atheist and you are a Christian. I fix computer monitors. I hope you had a vote in the local body elections. I will not ask if you voted for me! --Alan Liefting 03:55, 30 Sep 2004 (UTC)

Category:Wikipedians in New Zealand
Hi, You might want to consider adding User NZ res to the top of your user page, which will add you to this category automatically and also add a nice graphic. Onco_p53 08:42, 14 November 2005 (UTC)

Railway articles
Hi Patrick,

Firstly, I would like to thank you for the excellent New Zealand railway website you maintain, as it has proven invaluable to me. I'm a fellow New Zealand railfan (though unfortunately I'm presently stuck on the wrong side of the Tasman) and in my work to expand Wikipedia's coverage of New Zealand's railway lines and locomotives, your site has nicely complemented my collection of books, especially with regards to recent data.

Secondly, I was wondering if you would like to contribute any of your photographs to illustrate pages about specific locomotive classes, or to provide an image of a train in action on a specific line. You probably know more than I do about some lines too, and you can rest assurred that I would highly value any expansion of the articles I have started. The more on Wikipedia about New Zealand's trains, the better! If you would like to collaborate to more efficiently expand the information, I would certainly be open to that.

Have a good one! - Axver 13:47, 23 January 2006 (UTC)

Diesel Traction Group (NZ)
This is an automated message from CorenSearchBot. I have performed a web search with the contents of Diesel Traction Group (NZ), and it appears to be very similar to another wikipedia page: Diesel Traction Group. It is possible that you have accidentally duplicated contents, or made an error while creating the page— you might want to look at the pages and see if that is the case. If you are intentionally moving or duplicating content, please be sure you have followed the procedure at Splitting by acknowledging the duplication of material in edit summary to preserve attribution history.

This message was placed automatically, and it is possible that the bot is confused and found similarity where none actually exists. If that is the case, you can remove the tag from the article and it would be appreciated if you could drop a note on the maintainer's talk page. CorenSearchBot (talk) 09:37, 26 January 2009 (UTC)

Placing of content from "NZ Diesel and Electric Traction" website
This site closed 6 February 2009. As owner of the site and the content therein I assert my right to insert this content into Wikipedia pages and re-license it under the GFDL. Photographs from the site are displayed at http://picasaweb.google.com/enzedrail. PatrickDunfordNZ (talk) 03:20, 8 February 2009 (UTC)

Copyrights
Hello Patrick, I noticed you placed copypaste and close paraphrase tags on several train-related articles. You cited this book which unfortunately I cannot see. It is hard for me to confirm or help clean them up when I can't see the original text. Can you be of assistance in this matter? When you tagged the articles, they were automatically reported at Copyright problems/2011 April 24. Please feel free to comment there. Thanks.--NortyNort (Holla) 10:36, 3 May 2011 (UTC)

DG class article
Hi Patrick, can you please tag the parts of the DG article which are speculation? Cheers --LJ Holden 22:04, 30 September 2013 (UTC)

New login page
What a stupid log in page, case sensitive usernames, what a joke. PatrickDunfordNZ (talk) 01:37, 31 December 2013 (UTC)

ArbCom elections are now open!
MediaWiki message delivery (talk) 12:49, 23 November 2015 (UTC)

ArbCom 2023 Elections voter message
 Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add to your user talk page. MediaWiki message delivery (talk) 00:21, 28 November 2023 (UTC)

title: User talk:PatrickDunfordNZ


text:
Macintosh Classic II

The Macintosh Classic II (also sold as the Performa 200) is a personal computer designed and manufactured by Apple Computer, Inc. from October 1991 to September 1993. The system has a compact, appliance design with an integrated 9" monitor, typical of the earliest of the Macintosh range. A carrying handle moulded into the case added a degree of portability at a time when laptops were still relatively uncommon.

Like the preceding Macintosh SE/30, the Classic II was powered by a 16 MHz Motorola 68030 CPU but experienced about 30% slower performance due to the limitations imposed by a cost-reduced 16-bit data bus, versus the 32-bit bus used in the SE/30 design. The system had a base memory configuration of 2 MB, with a 10 MB upper limit and was supplied with either a 40 or 80 MB hard disk.

While the Classic II was styled after the earlier Classic, architecturally it had more in common with the Macintosh LC. The use of custom ICs, identical to those used in the LC, enabled the Classic II to have a lower component count than older Macs, which reduced manufacturing costs. Unlike the LC and the SE/30 before it, the Classic II lacked an internal Processor Direct Slot, making it the second slotless desktop Macintosh after the Classic.

The Classic II is one of three machines to be originally repackaged as a Macintosh Performa when the brand was first introduced in September 1992 to compete in the home user space. Called the "Performa 200", it was sold with the same specifications as the original Classic II but often supplied with bundled software. The exact packaged software varied by retailer but usually included the At Ease desktop alternative, which aimed to provide a simpler user interface experience than the standard Macintosh Finder. The Performa 200 was initially offered at a retail price of about $1,250 USD.

The Classic II is the last black-and-white compact Macintosh, and the last desktop Macintosh to include an external floppy disk drive port. Apple discontinued support for the Classic II on January 1, 2001.

Models

 * Macintosh Classic II: Sold in two configurations:
 * 2/40: 2 MB RAM, 40 MB HDD. USD $1,899.
 * 4/80: 4 MB RAM, 80 MB HDD. USD $2,399.
 * Macintosh Performa 200:

Hardware

Processor: 16 MHz (15.6672 MHz) Motorola 68030 (32-bit internally, 16-bit bus), with an optional Motorola 68882 FPU

RAM: 2 MB, expandable to 10 MB using two 100 ns 30-pin SIMMs

Display: 9" monochrome screen, 512 × 342 pixels

Audio: 8-bit mono 22 kHz

Hard drive: 40 or 80 MB

Floppy: 1.44 MB double-sided

Addressing: 24-bit or 32-bit

Battery: 3.6 V lithium

Expansion: Connectors on the rear panel include an ADB port for keyboard and mouse, two mini-DIN-8 RS-422 serial ports, DB-25 SCSI, DB-19 External floppy drive, and two 3.5 mm minijack audio sockets for audio in and headphone out.

The Classic II has a 50-pin internal expansion slot intended for either an FPU co-processor or additional ROM. The socket is unsuited for use as a general purpose expansion slot. Apple never produced an expansion card for this slot, although third-party FPUs were available including the FastMath Classic II by Applied Engineering and Sonnet offered a synchronous (16 MHz) and asynchronous (50 MHz) 68882 FPU. Retro computing hobbyists have also subsequently produced open-source designs for this slot. The main board from the Classic II (left) contains the logic for the system. High voltage components such as the PSU and CRT driver circuitry were on a separate "analogue" board. The 68030 CPU can be seen on the right, which is next to the FPU/ROM expansion slot. Two ROM chips in sockets are below the CPU. The RAM is to the bottom left. This model contains 4MB, of which 2MB is soldered to the board and 2MB is in SIMM sockets. Just above the RAM is the Apple "Eagle" chip which contains video interface circuitry and glue logic. Above that is an AMD manufactured SCSI controller and serial chip, close to an internal and external SCSI connector used to attach hard disks or other peripherals. There is a PRAM battery carrier to the left of the CPU (the battery is not present) with an internal floppy drive connector just above it with the floppy controller chip on the left. To the right of the floppy connector is an 8-bit microcontroller which manages the ADB bus.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Macintosh Classic II


text:
Talk:Jakarta Server Pages

This article way too detailed, or not detailed enough
If the Idea of this article is to give a good general impression on what JSP does for non-java people it is way too detailed. If the idea of this article is to give a detailed description on JSP technology, or maybe a starting guide for programmers, it's not detailed enough.

This article looks like a poorly written programer's guide, not an encyclopedia article! If anyone else agrees, I might be willing to chip in, and help do a complete rewrite.

Make sense?
"it is helpful to understand how the JSP compiler transforms the page into a Java servlet. For an example, see the following input, and its resulting generated Java servlet."'' in the introduction isn't followed by any "following" input. Am I being daft? └ UkPaolo/talk┐ 15:10, 27 January 2006 (UTC)

 * The examples are on separate pages. The word input links to JavaServer page example input and servlet links to JavaServer page example output. I think the text should be changed to make it more obvious what those links point to. – Doug B...........ell talk•contrib 16:16, 27 January 2006 (UTC)

 * Ah, I see, thank you! How strange, I've never seen separately linked examples like that in an article before. Its certainly confusing, and I would agree the text should be changed to make things more obvious... └ UkPaolo/talk┐ 16:29, 27 January 2006 (UTC)

 * I see the following discussion was previously listed here, and for some reason the discussion page blanked. I for one would have found it useful, and would support moving the examples to this article. Separate articles is not really inkeeping with the style of other articles... └ UkPaolo/talk┐ 16:36, 27 January 2006 (UTC)

 * The example input and output pages referenced by the this page are marked for cleanup. Should they be moved into a new "compiling" section of this page?  --lenehey

 * Yeah, they should be moved to this article. --Jonik 17:09, 13 August 2005 (UTC)
 * I'd support a merge with this article. └ UkPaolo/talk┐ 16:36, 27 January 2006 (UTC)

I have merged JavaServer_page_example_input and JavaServer_page_example_output into this article, see the new Example section. RossPatterson 16:59, 8 June 2006 (UTC)

The compiled code in "Resulting servlet" for the example included a call to a non-existent method "toStringOrBlank(...)". Since toStringOrBlank(...) is not a part of any standard Java/Servlet/JSP library, this method call would not be auto-generated by a JSP compiler. To make the example correct, I have added an implementation of toStringOrBlank(...) as an example of declaring a method within a <%! ... %> declaration block in the "Scripting elements" section. I've also added the call to toStringOrBlank(...) in the "Input JSP" section, and removed the comment about what toStringOrBlank(...) is supposed to do from the "Resulting servlet" section. Robert McGuire 20:17, 6 September 2007 (UTC)

Merger with "Model 2"
I don't think that a merger is appropriate. "Model 2" describes a design philosophy for WebApps. It is not necessarily linked to a certain view technology (JSP). You can (in theory) create a model 2 application while using another technology like Velocity as well (there are many very good MVC / Model 2 frameworks, so I wouldn't call this approach pratical). AnimalFriend 09:08, 3 September 2006 (UTC)

 * I.

First paragraph
The first paragraph is a poor introduction (not poorly written - may be in the wrong place) and references "static content".

A good intro should discuss the main attractions at a higher level. One of the main attraction of JSPs is the ability to dynamically generate content. Another attraction is the ability to mix standard java code and HTML including java scripts. Another attraction is JSPs are fast because the JSP container compiles JSPs into servlets keeps the resulting servlet in a fully compiled state.

Hope this helps HH

Comparison?
Perhaps a comparison of ASP vs. JSP vs. PHP? —The preceding unsigned comment was added by 70.101.158.1 (talk) 04:07, 19 December 2006 (UTC).

Criticism
Didn't this page used to have a criticisms section, whereas it cited problems with Java twisted to a web development platform

Tolland (talk) 19:58, 8 August 2022 (UTC) The following quote reads like the opinion of the author:

> Today there are several alternatives and a number of JSP-oriented pages in larger web apps are considered to be technical debt.

It's probably true. But if it's the opinion of someone notable, it should be referenced. Is it the opinion of the JCP, oracle, James Gosling or just some developer who has experience one too many null pointer errors??

Criticism and Comparison Sections Needed
I agree that this page could use a comparison section as well as a criticism section. As a Java web developer I am all too aware of the failings of developing directly using Java/JSP/JSTL/Servlets without additional technologies to ease the pain. —Preceding unsigned comment added by 64.201.43.121 (talk) 14:24, 3 June 2008 (UTC)

jsp:plugin section
The section about jsp:plugin seems to violate NPOV. There is alot of "hopefully" and 'X is poorly done.' Someone should revise this.

 * I did some work on that, but it could maybe use another look. AdjectiveAnimal 15:25, 5 July 2007 (UTC)

Good introduction to technology
The article looks like a good introduction to JSP technology for people already familiar with Java Servlet technology. I like code examples and short programmer's reference in Wikipedia. Both of nontechnical users and developers should be satisfied. —Preceding unsigned comment added by Vi2 (talk • contribs) 17:06, 27 April 2008 (UTC)

Developer not satisfied
This article is really not what I would expect at all. It has no history, or pedigree for the JSP (where does it fit in with PHP, ASP, etc?), at all, and basically acts a beginners guide. For people wanting to know the why, what and where of JSP this article doesn't really seem to answer it. Jimadilo (talk) 23:18, 22 December 2008 (UTC)
 * I have refactored the article to transform it to an encyclopedic article and I have moved the tutorial information there. Ftiercel (talk) 13:15, 18 September 2009 (UTC)

Errors
 — M3TA  (  info  ) @  09:50, 3 March 2010 (UTC)
 * 1) "This system of split inline coding sections is called step over scripting because it can wrap around the static markup by stepping over it." - I have never heard of this term, and the only place google can find it is in copies of this article.
 * 2) I don't like the whole description of 'runtime' compilation. That's exactly the opposite of what happens. JSPs are compiled into Servlets which are executed at runtime, possibly including output from other compiled JSPs. That's why you can pre-compile all your JSPs.
 * 3) I have a problem with the term JSP pages and I think it should be JSPs as a replacement.
 * 4) The JSP and compiled Java code in the example do not help or make anything clear, I think they should go, and be replaced with some simple examples of JSP syntax only, maybe with a description of the output. The Java generated is unimportant.

Work in progress
I'll be editing this article to have a better organizational structure, and I'll be removing some unnecessary/technical text as well as adding some information for people who are unfamiliar with Java servlets (and might be more familiar with PHP.) I'd like to add a criticism section, as well as a section with basic comparisons to PHP or ASP.NET for people who might be familiar with those technologies. If you have sources I could use for the criticism section, that would be helpful. --Libertyernie2 (talk) 16:17, 12 April 2012 (UTC)
 * Add encyclopedic content on this page and tutorial content on this one. Ftiercel (talk) 07:29, 13 April 2012 (UTC)
 * You've done a great job with this rewrite. The outline is logical, the examples are concise and are good representations of what JSP actually looks like. The comparison section is especially good. The compiler section could probably use a couple of sources, and you may want to think about adding in an example using JSTL.The only other criticisms I would have are some minor edit things; minor grammar fixes etc. Nice work. Ben.d.zimmer (talk) 16:33, 26 April 2012 (UTC)

Misleading caching section
The caching section in this article is roughly more about general web application scalability than it is about JSP caching. I'm not sure if it's still relevant, but O'Reilly has a page on it. And even if this were talking about a general Java web application, the content in this section is also refutable. — Preceding unsigned comment added by 111.94.212.83 (talk) 11:54, 29 November 2012 (UTC)

 * Yup. The "bottleneck" described has nothing to do with JSP or servlets, you got that with PHP or whatever else, too. I like the caching section, but it needs to be described more generally. The database is always the bottleneck, unless you're using a very fast "noSQL" database and a slow Apache server. 178.197.233.41 (talk) 12:04, 22 May 2013 (UTC)

 * Agreed. I've read through the section and it does seem a dubious one. There's certainly a space for improvements & citations there.Vaxquis (talk) 10:58, 9 June 2013 (UTC)

Yes, this section should simply be removed as it is. There is no content relevant to the subject of JSP technology. — Preceding unsigned comment added by Jjcroftiv (talk • contribs) 18:56, 5 September 2013 (UTC)

Done (be bold) Bramley (talk) 05:59, 21 February 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on JavaServer Pages. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive http://web.archive.org/web/20120419215245/http://java.sun.com:80/products/jsp/tutorial/TagLibraries3.html to http://java.sun.com/products/jsp/tutorial/TagLibraries3.html#63159

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.—cyberbot II  Talk to my owner :Online 17:58, 24 June 2016 (UTC)

title: Talk:Jakarta Server Pages


text:
Talk:List of programs broadcast by Global Television Network

I'm deleting the primetime schedule. It changes so often, and varies so much from region to region. Kirjtc2 03:32, 6 Aug 2004 (UTC)

Outdated infomation
This article currently has out-of-date info, for example: 90210 isn't currently airing it should be listed under Former Programming. Please help improve the page.

Factually Incorrect
The program "Border Security" is produced in Australlia & is highly unlikely to meet rules for Canadian Content; although it is marked as such.

Difficult to Maintain
Without a volunteer to constantly maintain this page it will become out of date, again, within a few weeks of any time that it is repaired. Perhaps it would be better just to delete it.
 * The beauty of Wikipedia is that ANYONE can edit it; if you see outdated information, feel free to update the page. There's no reason to delete an article simply because it is "outdated". █  EMARSEE   02:30, 10 February 2013 (UTC)

Unsourced date ranges
If the date ranges cannot be substantiated with references, I plan to cut them. Content must meet WP:V. So far, this is a glorified TV Guide list that doesn't meet WP:V. Cyphoidbomb (talk) 18:42, 28 May 2015 (UTC)

Global Television Network
Global Shows

Sharon, Lois & Bram Sing A to Z

The KangaZoo Club 2607:FEA8:C220:AD5:4D4D:663:7BBD:8CAA (talk) 00:15, 1 March 2023 (UTC)

 * Sing A to Z is an album, not a TV show. Ttwaring (talk) 00:27, 1 March 2023 (UTC)


text:
User:Wonderduck

I am a BSc.

so weit wie noch nie !

title: User:Wonderduck


text:
Underinsured

Underinsured refers to various degrees of being insured for some real risks and uninsured for others, at the same time.

Health care
Johns Hopkins University professor Vicente Navarro stated in 2003, "the problem does not end here, with the uninsured. An even larger problem is the underinsured" and "The most credible estimate of the number of people in the United States who have died because of lack of medical care was provided by a study carried out by Harvard Medical School Professors Himmelstein and Woolhandler (New England Journal of Medicine 336, no. 11, 1997). They concluded that almost 100,000 people died in the United States each year because of lack of needed care—three times the number of people who died of AIDS."

Auto insurance
In the auto insurance industry, underinsured motorist coverage is designed to protect motorists in the event that they have an accident with an at-fault underinsured motorist.

title: Underinsured


text:
Eagle Squadrons

The Eagle Squadrons were three fighter squadrons of the Royal Air Force (RAF) formed with volunteer pilots from the United States during the early days of World War II (1940), prior to United State's entry into the war in December 1941.

With the United States still neutral, many Americans simply crossed the border and joined the Royal Canadian Air Force (RCAF) to learn to fly and fight. Many early recruits had originally gone to Europe to fight for Finland against the Soviet Union in the Winter War.

Charles Sweeny, a wealthy businessman living in London, persuaded the British Government to form an RAF squadron composed of Americans. (His uncle, also named Charles Sweeny, had been working along similar lines, recruiting American pilots to fight in France. ) Sweeny's efforts were also coordinated in Canada by the World War I air ace Billy Bishop and the artist Clayton Knight, who formed the Clayton Knight Committee, which by the time the United States entered the war, had processed and approved 6,700 applications from Americans to join the RCAF or RAF. Sweeny and his rich society contacts bore the cost (over $100,000) of processing and sending the men to the United Kingdom for training.

Training

The basic requirements for joining the Eagle Squadron were a high school diploma, age 20 to 31 years, visual acuity of 20/40 correctable to 20/20, and 300 hours of certified flying time. These requirements, with the exception of the flight time, were not as strict as those required for service in the United States Army Air Corps, which was why some of the pilots joined the squadron. Most Eagle Squadron pilots did not have a college education or prior military experience.

Once in Britain and having passed basic flight training, the new pilots were sent for advanced operational training to an operational training unit (OTU) for two to four weeks to learn to fly Miles Master trainers, Hawker Hurricanes, and Supermarine Spitfires before being ostensibly commissioned as RAF officers and posted to front-line RAF fighter squadrons. The American pilots assigned to the Eagle Squadrons never renounced their US citizenship and although they wore the uniforms and held the rank titles of RAF officers, their dress and duty uniform tunics were modified with the Eagle Squadron patch, a white bald eagle flanked by the letters "ES" for Eagle Squadron.

Formation and evolution
Three Eagle Squadrons were formed between September 1940 and July 1941. On 29 September 1942, they were turned over to the Eighth Air Force of the U.S. Army Air Forces and became the 4th Fighter Group. Of the thousands who volunteered, only 244 Americans served with the Eagle Squadrons. Sixteen Britons also served as squadron and flight commanders.

The first Eagle Squadron, No. 71 Squadron, was formed in September 1940 as part of the RAF's buildup during the Battle of Britain, and became operational for defensive duties on 5 February 1941. 71 Squadron commenced operations based at RAF Church Fenton in early 1941, before a move to RAF Kirton-in-Lindsey. In April, the squadron transferred to RAF Martlesham Heath in Suffolk for operations over Europe. During May, it suffered its first loss when Mike Kolendorski was killed during a fighter sweep over the Netherlands. The intensity of operations stepped up with a move into No 11 Group of Fighter Command, being based at RAF North Weald by June 1941. On June 21, 1941, 22 year-old Nathaniel Maranz became the first American pilot to become a prisoner of war when he was shot down by a Bf 109 over the English Channel and picked up by a German patrol boat after swimming for an hour and a half. He was a prisoner in Stalag Luft III. The squadron's first confirmed victory came on 21 July 1941 when P/O William R. Dunn destroyed a Messerschmitt Bf 109F over Lille. In August, 71 Squadron replaced its Hurricanes and Spitfire Mk IIs, before quickly re-equipping with the latest Spitfire Mk Vs. The unit soon established a high reputation, and numerous air kill claims were made in RAF fighter sweeps over the continent during the summer and autumn of 1941. In December, the squadron was rested back at Martlesham Heath, before a move to Debden in May 1942.

The second Eagle Squadron, No. 121 Squadron, was formed at RAF Kirton-in-Lindsey in May 1941, flying Hurricanes on coastal convoy escort duties. On 15 September 1941, it destroyed its first German aircraft. The Hurricanes were replaced with Spitfires, and Spitfire Mk Vs arrived in November 1941. The following month, the squadron moved to RAF North Weald, replacing 71 Squadron. In 1942, its offensive activities over the English Channel included bomber escorts and fighter sweeps.

The third and final Eagle Squadron, No. 133 Squadron, was formed at RAF Coltishall in July 1941, flying the Hurricane Mk IIb. A move to RAF Duxford followed in August, and re-equipment with the Spitfire Mk V occurred early in 1942. In May, the squadron became part of the famed RAF Biggin Hill Wing. On 31 July 1942, during a bomber escort mission to Abbeville, 133's Spitfires fought 52-kill Luftwaffe 'ace' Oblt. Rudolf Pflanz of 11./JG 2 in combat; after shooting down one, Pflanz was himself shot down and killed in his Messerschmitt Bf 109G-1 over Berck-sur-Mer, France. 133 Squadron claimed three destroyed and one probable, while losing three aircraft. P/O "Jessie" Taylor accounted for two of the claims (a Bf 109F and an Focke-Wulf Fw 190) and P/O W. Baker was credited with a Fw 190 destroyed. On 26 September 1942, 11 of the unit's 12 brand new Spitfire Mk IXs were lost on a mission over Morlaix while escorting USAAF Boeing B-17 Flying Fortresses in heavy cloud cover. Strong winds blew the unit further south than realised and, short of fuel, the squadron let down directly over Brest. Six pilots were shot down and taken prisoner, four were killed, one bailed out and evaded capture, while one crash landed in England. One of the British pilots taken prisoner, Flight Lieutenant Gordon Brettell, was later to be shot as one of the escapees in The Great Escape from Stalag Luft III in 1944.

The Dieppe Raid was the only time all three Eagle Squadrons saw action operating together. No. 71 moved from Debden to Gravesend in mid-August in anticipation of the Dieppe action, while No. 121 operated from Southend. 133 Squadron moved with No. 401 Squadron RCAF from RAF Biggin Hill to Lympne on the English south coast. 71 Squadron claimed a Ju 88 shot down, 121 an Fw 190, while 133 claimed four Fw 190s, a Ju 88 and a Dornier Do 217. Six 'Eagle' Spitfires were lost, with one pilot taken prisoner and one killed. Through to the end of September 1942, the squadrons claimed to have destroyed 73½ German planes while 77 American and 5 British members were killed. 71 Squadron claimed 41 kills, 121 Squadron 18, and 133 Squadron 14½.

When informed of the attack on Pearl Harbor, most of the Eagle Squadron pilots wanted to immediately join the fight against Imperial Japan. Representatives from 71 and 121 Squadrons went to the American embassy in London and offered their services to the United States. The pilots from 71 Squadron decided they wanted to go to Singapore to fight the Japanese and a proposal was put to RAF Fighter Command, but it was turned down.

On 29 September 1942, the three squadrons were officially transferred from the RAF to the Eighth Air Force of the United States Army Air Forces, with the American pilots becoming officers in the USAAF. The Eagle pilots had earned 12 Distinguished Flying Crosses and one Distinguished Service Order. Only four of the 34 original Eagle pilots were still present when the squadrons joined the USAAF. Typical were the fates of the eight original pilots in the third squadron: Four died during training, one was disqualified, two died in combat, and one became a prisoner of war. About 100 Eagle pilots had been killed, were missing or were prisoners.

Negotiations regarding the transfer between the Eagle Squadrons, the USAAF and the RAF had to resolve a number of issues. The RAF wanted some compensation for losing three front-line squadrons in which they had heavily invested. Determining what rank each pilot would assume in the USAAF also had to be negotiated, with most being given a rank equivalent to their RAF rank. For example, a flight lieutenant became a USAAF captain, while a wing commander became a lieutenant colonel. None of the Eagle Squadron pilots had previously served in the USAAF and did not have US pilot wings. As such, it was decided that they be awarded USAAF pilot wings upon their transfer. Due to their insistence, the Eagle Squadron pilots who transferred to the USAAF 4th Fighter Group were permitted to retain their RAF wings, reduced in size, on the opposite side of their uniform to their new USAAF pilots wings.

Major General Carl Spaatz, head of the USAAF in Europe, wanted to spread the experience of the Eagles amongst various new US fighter squadrons, but the pilots of the three Eagle Squadrons wanted to stay together. The 71, 121, and 133 Squadrons were renamed by the USAAF as the 334th, 335th and 336th and transferred as complete units, retaining their Spitfires until P-47 Thunderbolts became available in January 1943. The 4th Fighter Group flew Spitfires until its conversion to P-47s was completed in April 1943. All three units had switched to the P-51 Mustang by the second half of March 1944. The 4th Fighter Wing, along with the 334th, 335th and 336th Fighter Squadrons, exist today as F-15E Strike Eagle units at Seymour Johnson Air Force Base in Goldsboro, North Carolina and are part of the Fifteenth Air Force.

Individual pilots

The first three members of the Eagle Squadrons were:

 * Vernon Charles "Shorty" Keough, service number 81620
 * Andrew B. Mamedoff, service number 81621
 * Eugene Quimby "Red" Tobin, service number 81622

All three had served together in No. 609 Squadron RAF, at RAF Middle Wallop. They had joined the RAF Volunteer Reserve (RAFVR) together (receiving consecutive service numbers), were posted to No. 609 Squadron RAF together, fought in the Battle of Britain together, and were transferred to 71 Squadron together in September 1940. The trio had also all been killed by the time of the transfer of the Eagle Squadrons to the USAAF in 1942 (from the database of the Commonwealth War Graves Commission (CWGC):

 * Pilot Officer Keough was killed in February 1941, age 29
 * Flight Lieutenant Mamedoff was killed in October 1941, age 29, after he had been transferred, with a promotion to be a flight commander, to another Eagle Squadron, No. 133 Squadron
 * Flying Officer Tobin was killed in September 1941, age 24

Phillip Leckrone, service number 84653, was another Battle of Britain veteran. He was also killed before the USAAF took charge of the Eagle Squadrons. Pilot Officer Leckrone was killed in January 1941, age 28.

The lives of these four pilots have been described in The Few by Alex Kershaw.

It is reported that Pilot Officer Art Donahue DFC stayed with the Eagle Squadron only a short time before requesting a transfer back to his original RAF unit. He did not appreciate the unruly behavior of many of the American pilots. He was killed in action in 1942.

Captain Don Gentile was a pilot with 133 Squadron, claiming two air victories, and by March 1944 had become the 4th Fighter Group's top ace in World War II, with 22 aerial kills.

Colonel Chesley "Pete" Peterson had 130 sorties with the Eagle Squadrons and became the youngest squadron commander in the RAF. When the Eagle Squadrons were transferred to the 4th Fighter Group, Peterson became the group's executive officer, succeeding to command of the group in April 1943, and becoming at 23 the youngest (at the time) colonel in the USAAF.

Colonel Donald Blakeslee was a pilot in 121 and 133 Squadrons during 1942, making 120 sorties and claiming three aerial kills. He became deputy commander of the 4th Fighter Group under Chesley Peterson, then commanded the group from January to October 1944.

Honours
The Eagle Squadrons Memorial is located on Grosvenor Square opposite a statue of Franklin D. Roosevelt.

British composer Kenneth J. Alford wrote a march, "Eagle Squadron", in honour of the pilots of the squadron. It is also a "thank you" to the American pilots: small sections of the Star Spangled Banner can be heard in the low brass during the trio.

General and cited references

 * Caine, Philip D. American Pilots in the RAF: The WWII Eagle Squadrons. Brassey's, 1993. ISBN 0-02-881070-8.
 * Childers, James Saxon. War Eagles: The Story of the Eagle Squadron. Windmill Press, 1943.
 * Republished by Eagle Publishing in 1983, ISBN 0-941624-71-4. Same as the 1943 edition, except it has an epilogue of the members as of 1982.
 * Donahue, Arthur Gerald. Tally-Ho! Yankee in a Spitfire. McMillan & Company, 1942.
 * Dunn, William R. Fighter Pilot: The First American Ace of World War II. University of Kentucky Press, 1982. ISBN 0-8131-1465-9.
 * Franks, Norman. The Greatest Air Battle: Dieppe, 19 August 1942. London: Grub Street, 1992. ISBN 0-948817-58-5.
 * Fydenchuk, W. Peter. Immigrants of War: Americans Serving With the RAF and RCAF During World War II. WPF Publications, 2005. ISBN 0-9737523-0-0.
 * Goodson, James A. and Norman Franks. Over-Paid, Over-Sexed and Over-Here. Wingham Press Ltd., 1991. ISBN 1-873454-09-0.
 * Goodson, James A. Tumult in the Clouds. NAL Trade, 2004. ISBN 0451211987
 * Haughland, Vern. Caged Eagles: Downed American Fighter Pilots, 1940–45. TAB Books, 1992. ISBN 0-8306-2146-6.
 * Haughland, Vern. The Eagle Squadrons: Yanks in the RAF, 1940–1942. Ziff-Davis Flying Books, 1979.
 * Republished by TAB Books in 1992, ISBN 0-8306-2146-6, with all the photos different from the 1st edition.
 * Haughland, Vern. The Eagles' War: The Saga of the Eagle Squadron Pilots, 1940–1945. Jason Aronson, Inc., 1982. ISBN 0-87668-495-9.
 * Republished by TAB Books in 1992, ISBN 0-8306-2145-8, with all the photos different from the 1st edition.
 * Holmes, Tony. American Eagles: American Volunteers in the R.A.F., 1937–1943. Classic Publications, 2001. ISBN 1-903223-16-4.
 * Kershaw, Alex. The Few. Da Capo Press, 2006. ISBN 0-306-81303-3.
 * Morris, John T. The Lives of an American Eagle. Mulberry River Press, 1999. ISBN 0-9636529-9-0.
 * Nelson, Kenneth James, CD. Spitfire RCW: The Wartime Exploits of Wing Commander Royce Clifford Wilkinson OBE, DFM & Bar, C.de G.(France). Hignall Printing Ltd., 1994.
 * Sweeny, Charles and Colonel James A. Goodson. Sweeny: The autobiography of Charles Sweeny. Harrop Press Ltd., 1990. ISBN 1-872809-00-6.

title: Eagle Squadrons


text:
Expedition 7

Expedition 7 was the seventh expedition to the International Space Station.

Mission parameters

 * Perigee: 384 km
 * Apogee: 396 km
 * Inclination: 51.6°
 * Period: 92 min

Mission objectives
The seventh crew of the International Space Station lifted off in Soyuz TMA-2 from the Russian Space Agency's Baikonur Cosmodrome in Kazakhstan on 25 April 2003, at 05:56:20 UTC. The Soyuz docked on 28 April 2003 and took over command of the ISS. The Space Shuttle fleet had been grounded due to the Columbia disaster, so the crew size was reduced to two, as opposed to the three that could be carried by the shuttle. The Expedition Seven crew—along with European Space Agency Astronaut Pedro Duque—landed back on Earth on 27 October 2003 at Kazakhstan at 02:41:20 UTC, after undocking from the International Space Station in their Soyuz spacecraft at 23:17 UTC.

Due to the reduced crew size, the scientific work had to be scaled down as well. Only 15 different experiments were conducted during the mission. Malenchenko and Lu were also tasked with periodic maintenance work on the station, as well as spacewalk training (although no spacewalks were planned). Supplies were delivered by Progress M1-10 in June and Progress M-48 in August.

From Houston, ISS Spacecraft Communicator Mike Fossum informed Expedition 7 Commander Yuri Malenchenko and Science Officer Edward Lu on 15 October 2003 of the successful launch of the Long March rocket carrying the Shenzhou 5 spacecraft and Chinese astronaut Yang Liwei. "It's really some exciting news to share. The world's spacefaring nations have been joined by a new member tonight: China."

"First off, we want to congratulate them," Lu replied. "The more people that go into space, the better off we all are. This is a great achievement and good for everyone in the long run." In Chinese, he later added, "Welcome to space. Have a safe journey."

"I would also like to say I love to have somebody else in space instead of me and Ed," said Malenchenko. "I also know this is great for thousands and thousands of people from China. I congratulate all of them."

Malenchenko and Lu were previously crewmates on the STS-106 shuttle mission and did a spacewalk together during that flight.

title: Expedition 7


text:
Content delivery network

A content delivery network or content distribution network (CDN) is a geographically distributed network of proxy servers and their data centers. The goal is to provide high availability and performance ("speed") by distributing the service spatially relative to end users. CDNs came into existence in the late 1990s as a means for alleviating the performance bottlenecks of the Internet as the Internet was starting to become a mission-critical medium for people and enterprises. Since then, CDNs have grown to serve a large portion of the Internet content today, including web objects (text, graphics and scripts), downloadable objects (media files, software, documents), applications (e-commerce, portals), live streaming media, on-demand streaming media, and social media sites.

CDNs are a layer in the internet ecosystem. Content owners such as media companies and e-commerce vendors pay CDN operators to deliver their content to their end users. In turn, a CDN pays Internet service providers (ISPs), carriers, and network operators for hosting its servers in their data centers.

CDN is an umbrella term spanning different types of content delivery services: video streaming, software downloads, web and mobile content acceleration, licensed/managed CDN, transparent caching, and services to measure CDN performance, load balancing, Multi CDN switching and analytics and cloud intelligence. CDN vendors may cross over into other industries like security, DDoS protection and web application firewalls (WAF), and WAN optimization.

Notable content delivery service providers include Cloudflare.

Technology
CDN nodes are usually deployed in multiple locations, often over multiple Internet backbones. Benefits include reducing bandwidth costs, improving page load times, and increasing the global availability of content. The number of nodes and servers making up a CDN varies, depending on the architecture, some reaching thousands of nodes with tens of thousands of servers on many remote points of presence (PoPs). Others build a global network and have a small number of geographical PoPs. Requests for content are typically algorithmically directed to nodes that are optimal in some way. When optimizing for performance, locations that are best for serving content to the user may be chosen. This may be measured by choosing locations that are the fewest hops, the lowest number of network seconds away from the requesting client, or the highest availability in terms of server performance (both current and historical), to optimize delivery across local networks. When optimizing for cost, locations that are the least expensive may be chosen instead. In an optimal scenario, these two goals tend to align, as edge servers that are close to the end user at the edge of the network may have an advantage in performance or cost.

Most CDN providers will provide their services over a varying, defined, set of PoPs, depending on the coverage desired, such as United States, International or Global, Asia-Pacific, etc. These sets of PoPs can be called "edges", "edge nodes", "edge servers", or "edge networks" as they would be the closest edge of CDN assets to the end user.

Security and privacy
CDN providers profit either from direct fees paid by content providers using their network, or profit from the user analytics and tracking data collected as their scripts are being loaded onto customers' websites inside their browser origin. As such these services are being pointed out as potential privacy intrusions for the purpose of behavioral targeting and solutions are being created to restore single-origin serving and caching of resources.

In particular, a website using a CDN may violate the EU's General Data Protection Regulation (GDPR). For example, in 2021 a German court forbade the use of a CDN on a university website, because this caused the transmission of the user's IP address to the CDN, which violated the GDPR.

CDNs serving JavaScript have also been targeted as a way to inject malicious content into pages using them. Subresource Integrity mechanism was created in response to ensure that the page loads a script whose content is known and constrained to a hash referenced by the website author.

Content networking techniques
The Internet was designed according to the end-to-end principle. This principle keeps the core network relatively simple and moves the intelligence as much as possible to the network end-points: the hosts and clients. As a result, the core network is specialized, simplified, and optimized to only forward data packets. Content Delivery Networks augment the end-to-end transport network by distributing on it a variety of intelligent applications employing techniques designed to optimize content delivery. The resulting tightly integrated overlay uses web caching, server-load balancing, request routing, and content services.

Web caches store popular content on servers that have the greatest demand for the content requested. These shared network appliances reduce bandwidth requirements, reduce server load, and improve the client response times for content stored in the cache. Web caches are populated based on requests from users (pull caching) or based on preloaded content disseminated from content servers (push caching).

Server-load balancing uses one or more techniques including service-based (global load balancing) or hardware-based (i.e. layer 4–7 switches, also known as a web switch, content switch, or multilayer switch) to share traffic among a number of servers or web caches. Here the switch is assigned a single virtual IP address. Traffic arriving at the switch is then directed to one of the real web servers attached to the switch. This has the advantage of balancing load, increasing total capacity, improving scalability, and providing increased reliability by redistributing the load of a failed web server and providing server health checks.

A content cluster or service node can be formed using a layer 4–7 switch to balance load across a number of servers or a number of web caches within the network.

Request routing directs client requests to the content source best able to serve the request. This may involve directing a client request to the service node that is closest to the client, or to the one with the most capacity. A variety of algorithms are used to route the request. These include Global Server Load Balancing, DNS-based request routing, Dynamic metafile generation, HTML rewriting, and anycasting. Proximity—choosing the closest service node—is estimated using a variety of techniques including reactive probing, proactive probing, and connection monitoring.

CDNs use a variety of methods of content delivery including, but not limited to, manual asset copying, active web caches, and global hardware load balancers.

Content service protocols
Several protocol suites are designed to provide access to a wide variety of content services distributed throughout a content network. The Internet Content Adaptation Protocol (ICAP) was developed in the late 1990s to provide an open standard for connecting application servers. A more recently defined and robust solution is provided by the Open Pluggable Edge Services (OPES) protocol. This architecture defines OPES service applications that can reside on the OPES processor itself or be executed remotely on a Callout Server. Edge Side Includes or ESI is a small markup language for edge-level dynamic web content assembly. It is fairly common for websites to have generated content. It could be because of changing content like catalogs or forums, or because of the personalization. This creates a problem for caching systems. To overcome this problem, a group of companies created ESI.

Peer-to-peer CDNs
In peer-to-peer (P2P) content-delivery networks, clients provide resources as well as use them. This means that, unlike client–server systems, the content-centric networks can actually perform better as more users begin to access the content (especially with protocols such as Bittorrent that require users to share). This property is one of the major advantages of using P2P networks because it makes the setup and running costs very small for the original content distributor.

Private CDNs
If content owners are not satisfied with the options or costs of a commercial CDN service, they can create their own CDN. This is called a private CDN. A private CDN consists of PoPs (points of presence) that are only serving content for their owner. These PoPs can be caching servers, reverse proxies or application delivery controllers. It can be as simple as two caching servers, or large enough to serve petabytes of content.

Large content distribution networks may even build and set up their own private network to distribute copies of content across cache locations. Such private networks are usually used in conjunction with public networks as a backup option in case the capacity of the private network is not enough or there is a failure which leads to capacity reduction. Since the same content has to be distributed across many locations, a variety of multicasting techniques may be used to reduce bandwidth consumption. Over private networks, it has also been proposed to select multicast trees according to network load conditions to more efficiently utilize available network capacity.

Emergence of telco CDNs
The rapid growth of streaming video traffic uses large capital expenditures by broadband providers in order to meet this demand and retain subscribers by delivering a sufficiently good quality of experience.

To address this, telecommunications service providers have begun to launch their own content delivery networks as a means to lessen the demands on the network backbone and reduce infrastructure investments.

Telco CDN advantages
Because they own the networks over which video content is transmitted, telco CDNs have advantages over traditional CDNs. They own the last mile and can deliver content closer to the end-user because it can be cached deep in their networks. This deep caching minimizes the distance that video data travels over the general Internet and delivers it more quickly and reliably.

Telco CDNs also have a built-in cost advantage since traditional CDNs must lease bandwidth from them and build the operator's margin into their own cost model. In addition, by operating their own content delivery infrastructure, telco operators have better control over the utilization of their resources. Content management operations performed by CDNs are usually applied without (or with very limited) information about the network (e.g., topology, utilization etc.) of the telco-operators with which they interact or have business relationships. These pose a number of challenges for the telco-operators who have a limited sphere of action in face of the impact of these operations on the utilization of their resources.

In contrast, the deployment of telco-CDNs allows operators to implement their own content management operations, which enables them to have a better control over the utilization of their resources and, as such, provide better quality of service and experience to their end users.

Federated CDNs and Open Caching
In June 2011, StreamingMedia.com reported that a group of TSPs had founded an Operator Carrier Exchange (OCX) to interconnect their networks and compete more directly against large traditional CDNs like Akamai and Limelight Networks, which have extensive PoPs worldwide. This way, telcos are building a Federated CDN offering, which is more interesting for a content provider willing to deliver its content to the aggregated audience of this federation.

It is likely that in a near future, other telco CDN federations will be created. They will grow by enrollment of new telcos joining the federation and bringing network presence and their Internet subscriber bases to the existing ones.

The Open Caching specification by Streaming Media Alliance defines a set of APIs that allows a Content Provider to deliver its content using several CDNs in a consistent way, seeing each CDN provider the same way through these APIs.

Improving CDN performance using Extension Mechanisms for DNS

Traditionally, CDNs have used the IP of the client's recursive DNS resolver to geo-locate the client. While this is a sound approach in many situations, this leads to poor client performance if the client uses a non-local recursive DNS resolver that is far away. For instance, a CDN may route requests from a client in India to its edge server in Singapore, if that client uses a public DNS resolver in Singapore, causing poor performance for that client. Indeed, a recent study showed that in many countries where public DNS resolvers are in popular use, the median distance between the clients and their recursive DNS resolvers can be as high as a thousand miles. In August 2011, a global consortium of leading Internet service providers led by Google announced their official implementation of the edns-client-subnet IETF Internet Draft, which is intended to accurately localize DNS resolution responses. The initiative involves a limited number of leading DNS service providers, such as Google Public DNS, and CDN service providers as well. With the edns-client-subnet EDNS0 option, CDNs can now utilize the IP address of the requesting client's subnet when resolving DNS requests. This approach, called end-user mapping, has been adopted by CDNs and it has been shown to drastically reduce the round-trip latencies and improve performance for clients who use public DNS or other non-local resolvers. However, the use of EDNS0 also has drawbacks as it decreases the effectiveness of caching resolutions at the recursive resolvers, increases the total DNS resolution traffic, and raises a privacy concern of exposing the client's subnet.

Virtual CDN (vCDN)
Virtualization technologies are being used to deploy virtual CDNs (vCDNs) with the goal to reduce content provider costs, and at the same time, increase elasticity and decrease service delay. With vCDNs, it is possible to avoid traditional CDN limitations, such as performance, reliability and availability since virtual caches are deployed dynamically (as virtual machines or containers) in physical servers distributed across the provider's geographical coverage. As the virtual cache placement is based on both the content type and server or end-user geographic location, the vCDNs have a significant impact on service delivery and network congestion.

Image Optimization and Delivery (Image CDNs)
In 2017, Addy Osmany of Google started referring to software solutions that could integrate naturally with the Responsive Web Design paradigm (with particular reference to the element) as Image CDNs. The expression referred to the ability of a web architecture to serve multiple versions of the same image through HTTP, depending on the properties of the browser requesting it, as determined by either the browser or the server-side logic. The purpose of Image CDNs was, in Google's vision, to serve high-quality images (or, better, images perceived as high-quality by the human eye) while preserving download speed, thus contributing to a great User experience (UX).

Arguably, the Image CDN term was originally a misnomer, as neither Cloudinary nor Imgix (the examples quoted by Google in the 2017 guide by Addy Osmany) were, at the time, a CDN in the classical sense of the term. Shortly afterwards, though, several companies offered solutions that allowed developers to serve different versions of their graphical assets according to several strategies. Many of these solutions were built on top of traditional CDNs, such as Akamai, CloudFront, Fastly, Edgecast and Cloudflare. At the same time, other solutions that already provided an image multi-serving service joined the Image CDN definition by either offering CDN functionality natively (ImageEngine) or integrating with one of the existing CDNs (Cloudinary/Akamai, Imgix/Fastly).

While providing a universally agreed-on definition of what an Image CDN is may not be possible, generally speaking, an Image CDN supports the following three components:

 * A Content Delivery Network (CDN) for the fast serving of images.
 * Image manipulation and optimization, either on-the-fly through URL directives, in batch mode (through manual upload of images) or fully automatic (or a combination of these).
 * Device Detection (also known as Device Intelligence), i.e. the ability to determine the properties of the requesting browser and/or device through analysis of the User-Agent string, HTTP Accept headers, Client-Hints or JavaScript.

The following table summarizes the current situation with the main software CDNs in this space:

Free CDNs

 * cdnjs
 * BootstrapCDN
 * Cloudflare
 * JSDelivr

Traditional commercial CDNs

 * Akamai Technologies
 * Amazon CloudFront
 * Aryaka
 * Ateme CDN
 * Azure CDN
 * CacheFly
 * CDNetworks
 * CenterServ
 * ChinaCache
 * Cloudflare
 * Cotendo
 * Edgio, formed through merger of EdgeCast Networks, Layer0 and Limelight Networks
 * Fastly
 * Gcore
 * Google Cloud CDN
 * HP Cloud Services
 * Incapsula
 * Instart
 * Internap
 * LeaseWeb
 * Lumen Technologies, formerly Level 3 Communications
 * MetaCDN
 * NACEVI
 * OnApp
 * GoDaddy
 * OVHcloud
 * Rackspace Cloud Files
 * Speedera Networks
 * StreamZilla
 * Wangsu Science & Technology
 * Yottaa

Telco CDNs

 * AT&T Inc.
 * Bharti Airtel
 * Bell Canada
 * BT Group
 * China Telecom
 * Chunghwa Telecom
 * Deutsche Telekom
 * KT
 * KPN
 * Lumen Technologies, formerly CenturyLink
 * Megafon
 * NTT
 * Pacnet
 * PCCW
 * Singtel
 * SK Broadband
 * Spark New Zealand
 * Tata Communications
 * Telecom Argentina
 * Telefonica
 * Telenor
 * TeliaSonera
 * Telin
 * Telstra
 * Telus
 * TIM
 * Türk Telekom
 * Verizon

Commercial CDNs using P2P for delivery

 * BitTorrent, Inc.
 * Internap
 * Pando Networks
 * Rawflow

Multi CDN

 * MetaCDN
 * Warpcache

In-house CDN

 * Netflix

title: Content delivery network