if you are loading a website over HTTP and you get stuck loading a huge image, you have no choice but to open up another socket connection or else wait
I think your confusing the HTTP protocol with BSD sockets. Your example is an HTTP 1.0 limitation, check out HTTP pipelining.
A socket is at it's very basic a read/write file handle. You can implement asynchronous handling, write your own protocol and do lots of extreme goodness. If you choose to be protocol stupid about how you transport your data then you live with the consequences.
As a network protocol engineer, you must look at minimum guaranteed latency, pick an average guaranteed bandwidth and taylor your protocol & packet sizes as necessary.
Writing a protocol is difficult when you care about performance and error handling.
IMHO, HTTP should have allowed a UDP pipelined transport mode . The overhead savings would have been worth the hassle.
Moreover - blame politicians for ENGINEERING a political class totally dependent on his hand. It's brilliant - voters who depend on government assistance have practically no choice but to vote for the guy. And yes - I'm looking at republicans AND democrats.
Can anyone explain how congress can get a measly 13% approval rating and still re-elect over 90% of it's members in the same month?
We're paid shills... we're paid in peanuts, jelly donuts, and mexican jumping beans. On a side note... would you like to win fabulous prizes every hour? Your free iPod has just arrived!
Well Damn... at the very least can we have your zip code?
Facilities & rent, benefits, insurance, lawyers, lawyers, lawyers, executive lamborghini, and a steady stream of vaporized LSD pumped in through the ventilators.
The first year they just lay there staring at the ceiling. Finally someone yells "OMG. I think it's going to EAT ME!!"
After that, the game design gets a lot easier. Everybody's pretty much onto the same vision, and you can feel a synergy about the place. Especially when you lick the windows.
At my high school there was a normal Physics class, but a separate after school lab. Our teacher lured us in with free computers, and challenged us with experiments while we were there. The lab has oscilloscopes, a/d converters, lasers, electronics - basically a physics funhouse.
It's the materials & it's the tools. Clean rooms, pure materials, testing equipment, chemicals. Even if we went for the lowest tech possible (60's era transistors, resistors, caps, core mem) you're still talking a couple of decades to identify material sources and refine techniques.
if you were in the woods with nothing but a hatchet, how long before you could send an email?
Even if you knew everything - it would literally take decades to do it "right." It took the entire human race with practically unlimited resources about 132 years once we had the most basic understanding of electronics (telephone). Even knowing every concept doesn't put you ahead by much without an existing manufacturing base.
I wouldn't suggest playing hardball - it's better to give them simply, basic professional terms (in writing) and just move on. If a lawsuit arrises from either side, you'll be much better positioned.
The point is that sometimes, no matter what you do - companies act irrationally and neurotic. Treat your colleagues well, inform your managers of your intentions and set firm boundaries.
So then those people won't have access to news stories... perhaps just the first paragraph.
The fact is that news costs money. I don't know the specifics of how such a system would work without being intrusive - but people can't work for free (just like you and me).
Unless you sing in a ridiculous leather jacket, I don't think you're going to get in trouble. The fact is that you work in different fields and attended different universities.
Besides - your legal record would show any abnormalities - and most companies do perform a criminal background check for professional positions.
The cost isn't outrageous. Encryption products have a much higher quality bar than most other products.
First - you really need experienced security developers. There aren't a lot of us out there. Second, there's a massive amount of auditing that happens. Algorithms, code implementation, UI interfaces, key storage. Everything has to be secure - or at the least fail gracefully without exposing key material or unsecured data.
Lastly, of course if you want the government to use your nifty products, your product must complete FIPS 140.2 testing through an outside lab (not cheap).
Nobody deals with that, for the moment. I don't think the hardware solutions deal with that for every case, either.
I've heard of some possible solutions being thrown out there - including a CPU "disabled cache"-type software solutions - but there's nothing being sold yet.
I love this book. Calculus explained for normal people. It goes a little fast in the beginning - but it's a refreshing, down to earth book that explains the what and why of calculus.
The difference between Mono & Samba is that C# is dev language.
If, for instance, Samba is sued into oblivion by Microsoft then we loose a single application. Yes, it's sad and everybody cries... but there's technical ways to solve that problem that are relatively doable - such as developing a new NAS network transport protocol that doesn't break any patents.
Alternatively, if Microsoft sues Mono into oblivion - and we've all been happily developing C# code for hundreds of applications - then it's going to be a total meltdown.
To be honest though - there's not much of a chance that either of those things are going to happen.
I like C# - it's a smart, clean language. I don't utilize much beyond the stock language (2.0 & generics) and don't see much need too.
There's been a lot of work in this area, getting around the hypervisor has been done, and even a Xorg driver(PS3RSX Binary Driver) - but only for older firmwares than 2.10.
So, if you want to run older firmware - you can run compiz. Of course - this probably prohibits newer games.
The difference was obviously in filesystem locking.
As someone who actually has experience developing samba code, I can say that the likely problem you hit was a combination of filesystem locking speeds (locking is done per file and by a region of space within a file and managed in the kernel filesystem) and this is mirrored to other samba processes through a shared-locking file (which is managed in a shared database-like file).
Only recently with Samba4 has locking been tackled (mostly for clustered filesystems) and ext3 filesystem locking has been greatly improved on Linux as well.
Slashdot Mirror
if you are loading a website over HTTP and you get stuck loading a huge image, you have no choice but to open up another socket connection or else wait
I think your confusing the HTTP protocol with BSD sockets. Your example is an HTTP 1.0 limitation, check out HTTP pipelining.
A socket is at it's very basic a read/write file handle. You can implement asynchronous handling, write your own protocol and do lots of extreme goodness. If you choose to be protocol stupid about how you transport your data then you live with the consequences.
As a network protocol engineer, you must look at minimum guaranteed latency, pick an average guaranteed bandwidth and taylor your protocol & packet sizes as necessary.
Writing a protocol is difficult when you care about performance and error handling.
IMHO, HTTP should have allowed a UDP pipelined transport mode . The overhead savings would have been worth the hassle.
Give this man a point.
Moreover - blame politicians for ENGINEERING a political class totally dependent on his hand. It's brilliant - voters who depend on government assistance have practically no choice but to vote for the guy. And yes - I'm looking at republicans AND democrats.
Can anyone explain how congress can get a measly 13% approval rating and still re-elect over 90% of it's members in the same month?
We're paid shills... we're paid in peanuts, jelly donuts, and mexican jumping beans. On a side note... would you like to win fabulous prizes every hour? Your free iPod has just arrived!
Well Damn... at the very least can we have your zip code?
Sheesh! like he probably meant the Declaration of Independence...
Yeah...
Facilities & rent, benefits, insurance, lawyers, lawyers, lawyers, executive lamborghini, and a steady stream of vaporized LSD pumped in through the ventilators.
The first year they just lay there staring at the ceiling. Finally someone yells "OMG. I think it's going to EAT ME!!"
After that, the game design gets a lot easier. Everybody's pretty much onto the same vision, and you can feel a synergy about the place. Especially when you lick the windows.
You need to learn some basic assembler - if only to become familiar with registers, integer, floating and mmu units, etc...
That's where we begin to understand hard limits like throughput, algorithm efficiency, and i/o.
At my high school there was a normal Physics class, but a separate after school lab. Our teacher lured us in with free computers, and challenged us with experiments while we were there. The lab has oscilloscopes, a/d converters, lasers, electronics - basically a physics funhouse.
It's the materials & it's the tools. Clean rooms, pure materials, testing equipment, chemicals. Even if we went for the lowest tech possible (60's era transistors, resistors, caps, core mem) you're still talking a couple of decades to identify material sources and refine techniques.
if you were in the woods with nothing but a hatchet, how long before you could send an email?
Even if you knew everything - it would literally take decades to do it "right." It took the entire human race with practically unlimited resources about 132 years once we had the most basic understanding of electronics (telephone). Even knowing every concept doesn't put you ahead by much without an existing manufacturing base.
What wretched idealistic bull... Is "righteous entitlement" nihilistic speak for "paying fair money for a product?"
Some people don't value their money? Remaining within the legal boundaries?
Not everybody is a drug running hitman? Must be exciting!
Which comes from Pascal - which has always had the length at the beginning. Hence why pascal strings always had limits.
I wouldn't suggest playing hardball - it's better to give them simply, basic professional terms (in writing) and just move on. If a lawsuit arrises from either side, you'll be much better positioned.
The point is that sometimes, no matter what you do - companies act irrationally and neurotic. Treat your colleagues well, inform your managers of your intentions and set firm boundaries.
So then those people won't have access to news stories... perhaps just the first paragraph.
The fact is that news costs money. I don't know the specifics of how such a system would work without being intrusive - but people can't work for free (just like you and me).
Unless you sing in a ridiculous leather jacket, I don't think you're going to get in trouble. The fact is that you work in different fields and attended different universities.
Besides - your legal record would show any abnormalities - and most companies do perform a criminal background check for professional positions.
First, the little penguin bites Linus, and now it bites the internet!!
The cost isn't outrageous. Encryption products have a much higher quality bar than most other products.
First - you really need experienced security developers. There aren't a lot of us out there.
Second, there's a massive amount of auditing that happens. Algorithms, code implementation, UI interfaces, key storage. Everything has to be secure - or at the least fail gracefully without exposing key material or unsecured data.
Lastly, of course if you want the government to use your nifty products, your product must complete FIPS 140.2 testing through an outside lab (not cheap).
Nobody deals with that, for the moment. I don't think the hardware solutions deal with that for every case, either.
I've heard of some possible solutions being thrown out there - including a CPU "disabled cache"-type software solutions - but there's nothing being sold yet.
I love this book. Calculus explained for normal people. It goes a little fast in the beginning - but it's a refreshing, down to earth book that explains the what and why of calculus.
It's by Silvanus Thompson.
The difference between Mono & Samba is that C# is dev language.
If, for instance, Samba is sued into oblivion by Microsoft then we loose a single application. Yes, it's sad and everybody cries... but there's technical ways to solve that problem that are relatively doable - such as developing a new NAS network transport protocol that doesn't break any patents.
Alternatively, if Microsoft sues Mono into oblivion - and we've all been happily developing C# code for hundreds of applications - then it's going to be a total meltdown.
To be honest though - there's not much of a chance that either of those things are going to happen.
I like C# - it's a smart, clean language. I don't utilize much beyond the stock language (2.0 & generics) and don't see much need too.
The fathers of Unix, of course!
Ken Thompson
Dennis Richie
Brian Kernighan
Bill Joy
Alan glasser?
That's nice - I have always wanted a tool like this! Thanks!
I use museum names...
Of course! We invented everything...
Small per-sin fees, monthly subscription tithes, and even commodity indulgences with tiered discount models.
But now... we're GIVING IT AWAY! That's right.... Come on down and be sin-free TODAY!
- Subject to contract terms and dogma. Donations appreciated. Not valid in the States of Iran & Saudi Arabia.
Yes, I love being Catholic.
There's been a lot of work in this area, getting around the hypervisor has been done, and even a Xorg driver(PS3RSX Binary Driver) - but only for older firmwares than 2.10.
So, if you want to run older firmware - you can run compiz. Of course - this probably prohibits newer games.
I've seen this happen WAY TOO OFTEN. Heed this advice. Seek a lawyer.
The difference was obviously in filesystem locking.
As someone who actually has experience developing samba code, I can say that the likely problem you hit was a combination of filesystem locking speeds (locking is done per file and by a region of space within a file and managed in the kernel filesystem) and this is mirrored to other samba processes through a shared-locking file (which is managed in a shared database-like file).
Only recently with Samba4 has locking been tackled (mostly for clustered filesystems) and ext3 filesystem locking has been greatly improved on Linux as well.