BT have just this week installed fibre to my house. While most of the last mile is copper it is wrong to say "Everything is copper" particularly when you consider in a vast majority of cases now the cable from exchange to the cabinet is fibre.
I had the strangest problem with Swedes where they'd seem to speak perfect English, but repeatedly mishear me as saying something offensive and never stop to make sure.
Actually I think I mentioned "cutting myself shaving" to someone and they apparently to this day believe I'm suicidal.
Haven't seen it myself, but I'm guessing it's a bit Dunning-Kruger effect + unwillingness to ask outright (the average Swede don't want to look silly, etc). While we have a significant exposure to English, few of us regularly have casual conversations with native English speakers, so our vocabularies aren't as good as we tend to think.
With UE4 you can pay for a single month and retain full access to the tools you've paid for, you just don't get updates. What you could decide on doing is paying every few months when an update comes along that offers something you need / want.
Not only is the shared tier a preview product it also releases itself from memory when inactive which results in a slow warm up after this happens and a visitor lands on your site.
Great for a personal blog but for a business where your customers expect things instantly, it is not so good.
> it also releases itself from memory when inactive.
That's the nature of application pools in IIS. If the app pool goes inactive for a time, IIS kills the w3wp process running the app. You can set the timeout in the web.config (not in front of code right now, don't know the exact incantations). Does WAWS respect that?
Though, the shutdown would be a good thing for a small site like what WAWS is intended for, because when the site isn't running, it's not still using resources.
In my company's environment (our own datacenter), our monitoring tools keep the app pool from "timing out" because it hits a status page every 2 minutes. We manually (through a script) recycle app pools at a given time every night.
While that is absolutely true for IIS and the Shared tier in Azure Websites (although it's fully configurable if you own the IIS box[1]), Dedicated tiers (when you own the whole VM) in Azure have a feature called Always On[2] Where there is no idle Time-out on the app itself, so even if the app remained idle for days, w3wp process won't be killed. Also if the app happen to shutdown for any reason (machine restart, Azure Update, Windows Update, app crash, etc) Azure Websites will make sure to send a request to the app to start it up and warm it, then the app can use Application Initialization[3] to do any more complex warmup
You don't need to have external tool to keep the AppPool from timing out: right-click AppPool in IIS Manager > Advanced Settings > Idle Time-out: set to zero. Also, you don't need the script to reset it at certain time: right-click AppPool in IIS Manager > Recycling... > Specific time(s).
Continued attention in the media, I'm guessing. While this issue seems to have died down mostly (still going on Twitter a bit), it's important to patch this up properly so it doesn't affect recruiting talent.
Recently I have been working on a project with a client where we have been using SkyDrive and its online Excel for simple and basic collaboration on a few documents.
The thing that I love about this setup is having the original Excel document sat there on the skydrive ready to be edited in the full Excel when more advanced editing is required and seamlessly updated on the web (although not at the same time, which is something I hope will be possible in the future).
it is when they drip feed the world for sales instead of publishing the information freely in one lump and separately writing articles.
the whole situation stinks tbh. despite the damage to NSA and GCHQ a number of other unsavoury elements in government are really benefiting from this...
The "lump it" method doesn't work, it's top news for a day then everyone gets back to what they were doing.
Dripping it out better highlights the incompetence of those who were tasked to keep it all in check (including journalism as a whole) and the extravagance of what has been going on by matching the scale of the surveilance to the scale of reporting.
It also highlights hypocrisy, such as the initial Merkel reaction "how dare they! Oh, well carry on" with the reaction after the revelations that Merkel was spied on "How dare they! We can't let this go on".
Not acting because "unsavoury elements will benefit" would just lead to a paralysis, unsavoury elements always find a way to benefit, it's part of what makes them so unsavoury.
The drip-feeding has been great! We get to see officials grudgingly acknowledge the latest revelation, and flatly deny we're doing whatever will be released next. Over and over.
