Why are you only satisfied if the backend coder is explicitly creating/joining threads? You don't have to be the one deciding when threads get created in order to have them stepping on each others' toes.
Again, I'm not trying to be confrontational; just showing my web app ignorance. Or am I?
Consider slashdot. Look up at your URL bar. Notice that it looks you asked the server for a perl script (.pl), not an HTML file (.html). The server is configured to interpret that request as a request for the output given by that perl script (with the parameters given at the end of the URL). The perl script asks a database for some information on users, their comments, etc. so that it can construct an HTML page to send you. The backend coder in a web app writes HTML only in the sense that a compiler writer writes assembly. Slashdot is based on perl code that generates HTML code.
A simple, static web site is just some HTML files that a server sends out when a browser requests them, but when you write a web app that generates pages dynamically, the HTML sent to the browser is just what a program run by the web server generates as output. This program is invoked when someone asks the server for a page. Since the program doesn't continue running after generating the page to be served, web apps typically use a database backend to maintain persistent state (who's logged in, what they've posted, what privileges they have, etc.). If you have a lot of users active at once, the web server will have a bunch of threads operating at once, so there's potential for serious race condition issues.
I dunno, it looks to me like this test is about memorizing operator precedence >_> Barring issues not mentioned in the problem statement, I'm rather inclined to let the compiler handle optimization on this.
It "matters" if you try to write multiprocess/multithreaded code but aren't good at it, though that's mostly a question of what synchronization screwups you can make and still get code that seems correct when tested.
the pricing of carriers for data transport that take a larger chunk out of people's budgets than they should, making it that much harder for people to pony up for the value of the content they get through those carriers' pipes
Bah humbug. The actual content on most sites isn't all that large. Strip out the flash ads, images unrelated to the article, gratuitous javascript, etc., and you're left with the very small amount that actually matters.
Though that exception might just mean that all of the ISP service agreements in the future include a clause to the effect of "CUSTOMER requests that SERVICE PROVIDER prioritize access to those sites and services favored by SERVICE PROVIDER, selected at the discretion of SERVICE PROVIDER, and restrict access to those which compete against SERVICE PROVIDER."
The lawsuit I'll grant you, but no company has a moral imperative to support any open source project indefinitely.
General vexation on the part of the Java community does not require a violated moral imperative. Whether it is evil or not, the decision to drop OpenSolaris tells people something about Oracle's attitude towards the community. Having no moral obligation to do something does not give one a free pass with regard to others' perceptions.
But he wasn't responsible for it after he was terminated.
If he left the job (willingly or otherwise) and then divulged the root password to someone who wasn't supposed to have it, he'd definitely be walking on thin ice.
And you think a counterfeiter will trust homeless people with exchanging fake money for the real stuff?
The exchange can happen on the spot. The counterfeiter offers the hobo $100 for a fraction of that amount in small bills. The hobo might be suspicious, but he knows he'd be turning down a huge payoff. The counterfeiter isn't getting as much as he could for his "product," but he still gets far more than it costs to produce. He also filters it through someone who's unlikely to be willing/able to identify him to the authorities.
For a while now, I've been hoping we'd eventually see a court rule that the possibility of retroactive copyright extension is incompatible with the Constitution's wording ("for limited times"), and that Congress therefore does not have the power to grant copyright extensions.
and the buyer who suggests he should be entitled to such an offer
Slashdotters in general do not claim that there should be such an offer, just that such offers should be enforced like other offers (and those who are unable or unwilling to hold up their ends of such offers should not make them).
We fixed the issue, and even though we told them that speedtest.net isn't a good indicator of speed due to the technology at the site, they started complaining that they weren't getting 10mb/s on the internet now and only had 3mb/s.
How would you recommend users test the speeds of their connections?
Slashdot Mirror
And of particular relevance to this article: all of Michigan is included in the orange section.
So now we're back to the first paragraph of my previous post.
Consider slashdot. Look up at your URL bar. Notice that it looks you asked the server for a perl script (.pl), not an HTML file (.html). The server is configured to interpret that request as a request for the output given by that perl script (with the parameters given at the end of the URL). The perl script asks a database for some information on users, their comments, etc. so that it can construct an HTML page to send you. The backend coder in a web app writes HTML only in the sense that a compiler writer writes assembly. Slashdot is based on perl code that generates HTML code.
A simple, static web site is just some HTML files that a server sends out when a browser requests them, but when you write a web app that generates pages dynamically, the HTML sent to the browser is just what a program run by the web server generates as output. This program is invoked when someone asks the server for a page. Since the program doesn't continue running after generating the page to be served, web apps typically use a database backend to maintain persistent state (who's logged in, what they've posted, what privileges they have, etc.). If you have a lot of users active at once, the web server will have a bunch of threads operating at once, so there's potential for serious race condition issues.
I dunno, it looks to me like this test is about memorizing operator precedence >_>
Barring issues not mentioned in the problem statement, I'm rather inclined to let the compiler handle optimization on this.
It "matters" if you try to write multiprocess/multithreaded code but aren't good at it, though that's mostly a question of what synchronization screwups you can make and still get code that seems correct when tested.
Bah humbug. The actual content on most sites isn't all that large. Strip out the flash ads, images unrelated to the article, gratuitous javascript, etc., and you're left with the very small amount that actually matters.
It's not used for FM simplex, but it is used for moonbounce and terrestrial weak signal.
It's a $15 fee to take a license exam (and IIRC, the FCC doesn't necessarily get all of it), so it's probably not a huge revenue stream.
Unfortunately, my feed line broke when the roof dropped a slab of ice on it a couple days ago -_-
I had a housemate who set the house router up to deprioritize BitTorrent traffic so that it would not interfere with gaming.
Though that exception might just mean that all of the ISP service agreements in the future include a clause to the effect of "CUSTOMER requests that SERVICE PROVIDER prioritize access to those sites and services favored by SERVICE PROVIDER, selected at the discretion of SERVICE PROVIDER, and restrict access to those which compete against SERVICE PROVIDER."
General vexation on the part of the Java community does not require a violated moral imperative. Whether it is evil or not, the decision to drop OpenSolaris tells people something about Oracle's attitude towards the community. Having no moral obligation to do something does not give one a free pass with regard to others' perceptions.
The fact that you did not fully read my post.
What you're missing is that as things are now, I can see your site without your having to also pay my ISP.
http://www.msa.md.gov/msa/mdmanual/43const/html/00dec.html
Part 97 just regulates amateur radio, not regular phone lines.
IIRC, "About Me" is not covered by this. You can put info there to keep it private (for now, at least).
Most jobs I've had made me sign a nondisclosure agreement for which the protected information included passwords.
If he left the job (willingly or otherwise) and then divulged the root password to someone who wasn't supposed to have it, he'd definitely be walking on thin ice.
The exchange can happen on the spot. The counterfeiter offers the hobo $100 for a fraction of that amount in small bills. The hobo might be suspicious, but he knows he'd be turning down a huge payoff. The counterfeiter isn't getting as much as he could for his "product," but he still gets far more than it costs to produce. He also filters it through someone who's unlikely to be willing/able to identify him to the authorities.
So should I tell all my classmates that the reason they can't find jobs when they graduate is that they bought houses they couldn't afford?
For a while now, I've been hoping we'd eventually see a court rule that the possibility of retroactive copyright extension is incompatible with the Constitution's wording ("for limited times"), and that Congress therefore does not have the power to grant copyright extensions.
Slashdotters in general do not claim that there should be such an offer, just that such offers should be enforced like other offers (and those who are unable or unwilling to hold up their ends of such offers should not make them).
How would you recommend users test the speeds of their connections?