Pipelining already works, most clients just don't use it.
>...gzip and 7zip support.
Nearly all web servers already support gzip. HTTP 1.1 supports arbitrary compression protocols. Any server/client can add 7zip support right now, just put it in the "accept" header.
> All data is compressed by default
That's a terrible idea. All data is plain by default, and compressed any time the client says that they can understand compression. (Which is how HTTP/1.1 works) That should be almost all the time, of course, but I want to be able to use telnet to test a web server or make an extremely simple web server/client that doesn't need compression libraries. (I remember seeing a web server built into an RAJ-45 jack at one point...)
> Option to initiate persistant connection
HTTP/1.1 already supports that.
See a trend? HTTP/1.1 _is_ this wondrous "2.0" that you're asking for.
There must be 50 posts already saying basically: "Just compress the XML, duh!"
Compression is already in use on most servers, assuming the clients send the appropriate accept headers. The perceived sluggishness of XML is partly caused by the fact that the XML must be generated by the sender and than parsed by the receiver. Numeric values have to be converted from binary to ASCII-coded-decimal and back, strings have to be embedded and extracted, etc. I think this is the type of inefficiency that these people are trying to prevent.
That said, I think binary XML is a terrible idea. Keep using gzip on HTTP transfers and the technology will catch up shortly.
<?xml version="1.0"?> <flamebait audience="geeks"> The people complaining about XML being slow are probably using Java anyway. They should be used to their software being sluggish. </flamebait>
>To even out, there has to be a job somewhere
>that causes -1.5 people to be hired.
That just doesn't make any sense.
Imagine a group of 100 (working-age) people, 80 of whom have a job, 5 of the remainder are looking for work. The unemployment rate is 5%. One of them gets a job at Microsoft, requiring the local $tarbucks to hire 2 new coffee pimps. One nozzle jockey quits to become a caffeine dealer. There are now 82 people with jobs and the unemployment rate drops to 3%.
No, the FAA is responsible for maintaining the safety of that system. They failed bigtime by allowing Windows to be used for a mission-critical system.
Technically, a contractor was the one who made the decision, but the final responsibility for oversight rests on the FAA.
Unfortunately, I know some very smart people who will vote for Bush. Some of them have picked a specific issue (e.g. gun control) and ignore all the other issues. Others simply live in a delusional dreamland where Fox News is Fair and Balanced and all Republicans are "good guys" simply because they are Republicans. At least one is just an intolerant, homophobic, racist a**-hole, and knows "W" is with him all the way.
Oh, if only it were that simple. You could be 100% right with rock-solid proof, and you would still lose that case. Consider the SCO case for a moment, and IBM must have spent millions on that.
I think you only get a "free state lawyer" in criminal cases where the state is the plaintiff.
My day job is writing windows software, and I can tell you that usability is not something that can be unilaterally called a technical issue. Some usability issues like response time and the ability to access various features through more than one interface (e.g. menu, keyboard and context menu) can be stated as an issue and specifically checked off as completed. Engineers like this kind of thing. Other usability requirements like "good menu layout" and "clear feature separation" can't realy be quantified like that, which makes them difficult to manage.
I've been following Bruce's story for a while, and I just wish I could afford to have him build me something. I don't have an (big, evil) S.U.V., but I'd love to have a missile on my car. Perhaps a jet-powered motorcycle...
Anyway, if you're like me and you can drop a few dollars without ever missing it, here's the donations page:
His previous income was from aerospace projects in general, and he built a cruise missile to prove to his government that it could be done by a private party, when they would not listen to him. Now he's completely locked out of the aerospace industry in NZ, so he's given up on helping the gov. and looking to move out.
So you're saying he was an idiot for being patriotic and attempting to help secure his own country against terrorism? I'd say they are the idiots for not listeneing to him.
If he had a public e-mail address up, I would PayPal him a few bucks just because I think he got royally shafted. I'm going to try anyway, actually.
I'm guessing that most of you have the DeCSS source already, if not the t-shirt, but if you truncate the link, you get a source tree for 1.2.
There's also something about WMA in there. I have not looked at it, but I suspect that it's a way to circumvent the DRM that's built into the WMA format.
I have never found a software package that adequately replaces my Moleskine.
> pipelining...
...gzip and 7zip support.
Pipelining already works, most clients just don't use it.
>
Nearly all web servers already support gzip. HTTP 1.1 supports arbitrary compression protocols. Any server/client can add 7zip support right now, just put it in the "accept" header.
> All data is compressed by default
That's a terrible idea. All data is plain by default, and compressed any time the client says that they can understand compression. (Which is how HTTP/1.1 works) That should be almost all the time, of course, but I want to be able to use telnet to test a web server or make an extremely simple web server/client that doesn't need compression libraries. (I remember seeing a web server built into an RAJ-45 jack at one point...)
> Option to initiate persistant connection
HTTP/1.1 already supports that.
See a trend? HTTP/1.1 _is_ this wondrous "2.0" that you're asking for.
There must be 50 posts already saying basically:
"Just compress the XML, duh!"
Compression is already in use on most servers, assuming the clients send the appropriate accept headers. The perceived sluggishness of XML is partly caused by the fact that the XML must be generated by the sender and than parsed by the receiver. Numeric values have to be converted from binary to ASCII-coded-decimal and back, strings have to be embedded and extracted, etc. I think this is the type of inefficiency that these people are trying to prevent.
That said, I think binary XML is a terrible idea. Keep using gzip on HTTP transfers and the technology will catch up shortly.
<?xml version="1.0"?>
<flamebait audience="geeks">
The people complaining about XML being slow are probably using Java anyway. They should be used to their software being sluggish.
</flamebait>
>To even out, there has to be a job somewhere >that causes -1.5 people to be hired.
That just doesn't make any sense.
Imagine a group of 100 (working-age) people, 80 of whom have a job, 5 of the remainder are looking for work. The unemployment rate is 5%. One of them gets a job at Microsoft, requiring the local $tarbucks to hire 2 new coffee pimps. One nozzle jockey quits to become a caffeine dealer. There are now 82 people with jobs and the unemployment rate drops to 3%.
No, the FAA is responsible for maintaining the safety of that system. They failed bigtime by allowing Windows to be used for a mission-critical system. Technically, a contractor was the one who made the decision, but the final responsibility for oversight rests on the FAA.
This is great:
... according to a software analyst..."
"The shutdown is intended to keep the system from becoming overloaded with data
This "analyst" knows nothing about computers, works for Microsoft, or both.
>People with brains would never vote for Bush
Unfortunately, I know some very smart people who will vote for Bush. Some of them have picked a specific issue (e.g. gun control) and ignore all the other issues. Others simply live in a delusional dreamland where Fox News is Fair and Balanced and all Republicans are "good guys" simply because they are Republicans. At least one is just an intolerant, homophobic, racist a**-hole, and knows "W" is with him all the way.
Right on. I couldn't have said it better.
Yes, this has been pointed out several times.
If you're correct, why did so many people absolutely refuse to allow a recount to happen?
Anyone who was sure they had won would be happy to have a recount.
You like him that much, just from that short description? Maybe you should get to know him first...
The first post cannot be redundant.
I really, really hope that you're wrong.
Oh, if only it were that simple. You could be 100% right with rock-solid proof, and you would still lose that case. Consider the SCO case for a moment, and IBM must have spent millions on that.
I think you only get a "free state lawyer" in criminal cases where the state is the plaintiff.
My day job is writing windows software, and I can tell you that usability is not something that can be unilaterally called a technical issue. Some usability issues like response time and the ability to access various features through more than one interface (e.g. menu, keyboard and context menu) can be stated as an issue and specifically checked off as completed. Engineers like this kind of thing. Other usability requirements like "good menu layout" and "clear feature separation" can't realy be quantified like that, which makes them difficult to manage.
I've been following Bruce's story for a while, and I just wish I could afford to have him build me something. I don't have an (big, evil) S.U.V., but I'd love to have a missile on my car. Perhaps a jet-powered motorcycle...
Anyway, if you're like me and you can drop a few dollars without ever missing it, here's the donations page:
http://aardvark.co.nz/pjet/donations.shtml
His previous income was from aerospace projects in general, and he built a cruise missile to prove to his government that it could be done by a private party, when they would not listen to him. Now he's completely locked out of the aerospace industry in NZ, so he's given up on helping the gov. and looking to move out.
So you're saying he was an idiot for being patriotic and attempting to help secure his own country against terrorism? I'd say they are the idiots for not listeneing to him.
If he had a public e-mail address up, I would PayPal him a few bucks just because I think he got royally shafted. I'm going to try anyway, actually.
I'm guessing that most of you have the DeCSS source already, if not the t-shirt, but if you truncate the link, you get a source tree for 1.2.
There's also something about WMA in there. I have not looked at it, but I suspect that it's a way to circumvent the DRM that's built into the WMA format.