All the RAM is on CPU0, so if you need to access something on CPU1, you have to go over the HTT bus and wait for the other CPU to satisfy your request. While this is likely something that was due to it being a SFF computer, I find that disappointing.
My thinking was that people don't change platforms for their source code control systems all that often. When it happens, a utility can extract/merge the ID value.
But I was speaking more of on the client side, not on the server side. Honestly, I don't care how the repository stores it's data as long as it's reliable (coughcoughSourceSafecough). The client tool & the API hides all the messy details from me. On my desktop where I'm developing, I now have to track two files. A lot of the newer IDEs will recognize files in the project directory and put them into your project file automatically (BEA Workshop & Compuware Optimal J do this). So now your IDE is showing two files where you only care about one.
Just read some of the Arch whitepaper, and saw how it stores a file's unique identifier in a *.id file. I was thinking that on the NTFS filesystem, this could be stored in a second stream for each file under revision control, thus keeping your working directory "clean", and roughly half the size.
They've probably already thought of this;-) but I just thought I'd throw it out there.
I bought a USB keydrive at a computer show that still had stuff on it. The previous owner was apparantly a geologist working for various petroleum companies. He had some powerpoint slides in there that had his email address, so I was able to get in touch with him and send him a CDR with his files on it (he had already bought a replacement device). He didn't say how he lost/misplaced the drive -- might have actually been a cab or airport shuttle.
If the drive had contained photos, would I have posted them on the Internet? No, because they wouldn't have belonged to me. Would I have looked at them? Yes, I'm as curious as the next guy.
I saw it last night -- highly recommended. It will probably will come to be regarded as the "Star Wars" of this decade -- something that changed the entire nature of filmmaking.
There may not have been any sets, per-se, but there were a fair amount of props used in close-ups (like where the characters were leaning against a railing), so not absolutely everything was painted green.:-)
I got a call the other night from an automated poll taker:
"If you intend to vote for George Bush, press or say '1'.
If you intend to vote for John Kerry, press or say '2'.
If you are undecided, press or say '3'."
With NT 4.0, they moved the display drivers into the system space, not the entire GUI subsystem. This was for performance reasons.
I knew it was a bad idea, and I'm sure that there are those at Microsoft (Dave Cutler, probably) who thought it was a bad idea too. But it's a tradeoff, and at the time the business risk was considered acceptable because they had a driver certification program, and they were going to make sure that drivers would behave themselves.
Software Rentals was tried in the late 80's, but got squashed by the BSA and Microsoft, who were more interested in sales and upgrades, and were very concerned about piracy (think about all the people who rent a DVD from Blockbuster, rip their own copy, and return it never to rent it again). I think Beagle Brothers was one of the resellers that tried it... could be wrong (someone correct me if they know).
The authors talk convincingly about the price negotiation that might occur at the time of the service being delivered -- This implies that SOA will become part of a hyper-capitalistic market economy, where every time you want to spell-check your document, you would pay a different price, due to supply & demand on the supplier's systems. Or perhaps their CEO is sitting at his desk, clicking the "raise price" button so he can make his beach house payment..;-)
I'm not so convinced about their arguments -- one big assumption they make is that one service provider is much like any other, and that the API to each service is identical (i.e. no cost to changing service providers). I seriously doubt this will happen in practice... each supplier will probably have their own, incompatible API. Maybe over the long term a standard may arise (upon which it truly becomes a commodity), but that would require an 800-lb gorilla to set a standard.
Think about what this requires in the way of authentication & billing: For every provider you may want to use, you have to establish some credentials with them so they know how to charge you. It'd have to be a combination of something like Liberty Alliance or MS-Passport, combined with a micropayments scheme. This billing system would require it's own API, that both the user and the service supplier would have to support. Uh-oh, things just doubled in complexity!
I'm not saying such a thing won't come about -- I've been in the industry too long to discount such things -- but I think it's highly unlikely given the obstacles.
Chip H.
Disclaimer: I work at an ASP. Profitable and cash-flow positive!
Storing your files in a DB gets you at least three big advantages:
1) Vastly reduced fragmentation. You can store a couple of small files in a single DB page. Also, when a DB grows, it usually does it as a percentage, or as a large allocation (like a megabyte or more).
2) Finding your files. Like another poster said, finding a file from two years ago is just a matter of building the correct WHERE clause.
3) Arbitrary indexes. If I'm really into my music, I can build an index over my MP3 genre, artist, album, etc. If I'm a salesman, I can build an index (ok, ok, they'll use a wizard) over my contacts, so when I travel to another city, I can easily do a locality search, and make sales calls on people who have expressed interest in my product.
As a further extension of the arbitrary index idea -- imagine doing joins -- I can find the cover art for my MP3 by joining on the artist & album name.
Does all this slow things down? Sure. Everything is a tradeoff -- if you want more flexible searching, reduced fragmentation, etc. you have to pay the cost up front when you insert new rows.
I had a look at the specs, and they're a good example of why object-oriented programmers shouldn't write XML specs: They tend to turn everything into a complexType when there's no need.
Example: They defined a type called ArrayAssociativeType, and then used it to further define array and bag types. All they should have done is define a parent element that is named "plural" (like: <regions></regions>), that would naturally indicate that its contents can ocurr multiple times.
they are not afraid to do a recall, even if it's years after the product was released.
Not only that, but they're shipping the replacements in advance. Most companies would require you to send in the bad one first, leaving you dead in the water until the UPS ground delivery arrives.
If they're offering 1 million songs, I'm curious who they got to do the ripping? I have visions of a room full of trained monekys, putting CDs into drives in return for food pellets.
On a similar note: Which ripping software did they use? LAME? Something home-grown?
If you do get a credit card, get an American Express. The classic "green" one, not the "blue" one that lets you run up a balance. It forces you to pay it off every month.
In 1986 I was stationed at McClellan AFB, and got to watch some contractors install about 4 racks of beige equipment called an "Interface Message Processor" from a company called BBN. I had no clue at the time it was part of the internet. About ten years later I realized what it was, and thought "Wow, I got to see an IMP in person!"
Sorry, I don't have a photo (and couldn't find one via Google) -- cameras weren't allowed in the area. The very first IMPs looked like this, though.
I urge all of you that are parents, that once your children are old enough, you get them a full unrestricted adult library card.
I'm very grateful to my mom for doing this -- I wouldn't have been able to read "A Wrinkle in Time" in middle school otherwise. I'm also struck by a sense of "The more things change, the more they stay the same" -- middle school was 1977 for me, and the same thing was going on then.
Slashdot Mirror
All the RAM is on CPU0, so if you need to access something on CPU1, you have to go over the HTT bus and wait for the other CPU to satisfy your request. While this is likely something that was due to it being a SFF computer, I find that disappointing.
Chip H.
The benefit for this small group would essentially be paid for by all tax payers
I think you just described a large portion of goverment services, from unemployment benefits to welfare, to public transportation.
Chip H.
My thinking was that people don't change platforms for their source code control systems all that often. When it happens, a utility can extract/merge the ID value.
But I was speaking more of on the client side, not on the server side. Honestly, I don't care how the repository stores it's data as long as it's reliable (coughcoughSourceSafecough). The client tool & the API hides all the messy details from me. On my desktop where I'm developing, I now have to track two files. A lot of the newer IDEs will recognize files in the project directory and put them into your project file automatically (BEA Workshop & Compuware Optimal J do this). So now your IDE is showing two files where you only care about one.
Chip H.
Just read some of the Arch whitepaper, and saw how it stores a file's unique identifier in a *.id file. I was thinking that on the NTFS filesystem, this could be stored in a second stream for each file under revision control, thus keeping your working directory "clean", and roughly half the size.
;-) but I just thought I'd throw it out there.
They've probably already thought of this
Chip H.
It might be fun to put a bid in, just so you can say that you went up against Paul Allen on eBay.
Chip H.
What about a .owner file in the root directory with your contact info? Takes up a lot less space.
Chip H.
I bought a USB keydrive at a computer show that still had stuff on it. The previous owner was apparantly a geologist working for various petroleum companies. He had some powerpoint slides in there that had his email address, so I was able to get in touch with him and send him a CDR with his files on it (he had already bought a replacement device). He didn't say how he lost/misplaced the drive -- might have actually been a cab or airport shuttle.
If the drive had contained photos, would I have posted them on the Internet? No, because they wouldn't have belonged to me. Would I have looked at them? Yes, I'm as curious as the next guy.
Chip H.
I saw it last night -- highly recommended. It will probably will come to be regarded as the "Star Wars" of this decade -- something that changed the entire nature of filmmaking.
:-)
There may not have been any sets, per-se, but there were a fair amount of props used in close-ups (like where the characters were leaning against a railing), so not absolutely everything was painted green.
Chip H.
.. if you speak with a German accent. Chip H.
I thought the AS/400 had a 65th bit that indicated privledge level? Chip H.
I predict that "Star Wars: The 4:3 edition" will last only as long as the Star Trek animated series did. If not shorter. Chip H.
I got a call the other night from an automated poll taker:
"If you intend to vote for George Bush, press or say '1'.
If you intend to vote for John Kerry, press or say '2'.
If you are undecided, press or say '3'."
I pressed 4.
Chip H.
With NT 4.0, they moved the display drivers into the system space, not the entire GUI subsystem. This was for performance reasons.
I knew it was a bad idea, and I'm sure that there are those at Microsoft (Dave Cutler, probably) who thought it was a bad idea too. But it's a tradeoff, and at the time the business risk was considered acceptable because they had a driver certification program, and they were going to make sure that drivers would behave themselves.
Chip H.
Dispatchers will be able to control some of the cameras, such as panning and zooming in."
Hey Peter man, check out channel 9, it's the breast exams!
Chip H.
Software Rentals was tried in the late 80's, but got squashed by the BSA and Microsoft, who were more interested in sales and upgrades, and were very concerned about piracy (think about all the people who rent a DVD from Blockbuster, rip their own copy, and return it never to rent it again). I think Beagle Brothers was one of the resellers that tried it... could be wrong (someone correct me if they know).
;-)
... each supplier will probably have their own, incompatible API. Maybe over the long term a standard may arise (upon which it truly becomes a commodity), but that would require an 800-lb gorilla to set a standard.
The authors talk convincingly about the price negotiation that might occur at the time of the service being delivered -- This implies that SOA will become part of a hyper-capitalistic market economy, where every time you want to spell-check your document, you would pay a different price, due to supply & demand on the supplier's systems. Or perhaps their CEO is sitting at his desk, clicking the "raise price" button so he can make his beach house payment..
I'm not so convinced about their arguments -- one big assumption they make is that one service provider is much like any other, and that the API to each service is identical (i.e. no cost to changing service providers). I seriously doubt this will happen in practice
Think about what this requires in the way of authentication & billing: For every provider you may want to use, you have to establish some credentials with them so they know how to charge you. It'd have to be a combination of something like Liberty Alliance or MS-Passport, combined with a micropayments scheme. This billing system would require it's own API, that both the user and the service supplier would have to support. Uh-oh, things just doubled in complexity!
I'm not saying such a thing won't come about -- I've been in the industry too long to discount such things -- but I think it's highly unlikely given the obstacles.
Chip H.
Disclaimer: I work at an ASP. Profitable and cash-flow positive!
Storing your files in a DB gets you at least three big advantages:
1) Vastly reduced fragmentation. You can store a couple of small files in a single DB page. Also, when a DB grows, it usually does it as a percentage, or as a large allocation (like a megabyte or more).
2) Finding your files. Like another poster said, finding a file from two years ago is just a matter of building the correct WHERE clause.
3) Arbitrary indexes. If I'm really into my music, I can build an index over my MP3 genre, artist, album, etc. If I'm a salesman, I can build an index (ok, ok, they'll use a wizard) over my contacts, so when I travel to another city, I can easily do a locality search, and make sales calls on people who have expressed interest in my product.
As a further extension of the arbitrary index idea -- imagine doing joins -- I can find the cover art for my MP3 by joining on the artist & album name.
Does all this slow things down? Sure. Everything is a tradeoff -- if you want more flexible searching, reduced fragmentation, etc. you have to pay the cost up front when you insert new rows.
Chip H.
I had a look at the specs, and they're a good example of why object-oriented programmers shouldn't write XML specs: They tend to turn everything into a complexType when there's no need.
Example: They defined a type called ArrayAssociativeType, and then used it to further define array and bag types. All they should have done is define a parent element that is named "plural" (like: <regions></regions>), that would naturally indicate that its contents can ocurr multiple times.
Simplicity is a virtue, especially in XML.
Chip H.
they are not afraid to do a recall, even if it's years after the product was released.
Not only that, but they're shipping the replacements in advance. Most companies would require you to send in the bad one first, leaving you dead in the water until the UPS ground delivery arrives.
Kudos to IBM.
Chip H.
If they're offering 1 million songs, I'm curious who they got to do the ripping? I have visions of a room full of trained monekys, putting CDs into drives in return for food pellets.
On a similar note: Which ripping software did they use? LAME? Something home-grown?
Chip H.
If you do get a credit card, get an American Express. The classic "green" one, not the "blue" one that lets you run up a balance. It forces you to pay it off every month.
Chip H.
In 1986 I was stationed at McClellan AFB, and got to watch some contractors install about 4 racks of beige equipment called an "Interface Message Processor" from a company called BBN. I had no clue at the time it was part of the internet. About ten years later I realized what it was, and thought "Wow, I got to see an IMP in person!"
Sorry, I don't have a photo (and couldn't find one via Google) -- cameras weren't allowed in the area. The very first IMPs looked like this, though.
Chip H.
I urge all of you that are parents, that once your children are old enough, you get them a full unrestricted adult library card.
I'm very grateful to my mom for doing this -- I wouldn't have been able to read "A Wrinkle in Time" in middle school otherwise. I'm also struck by a sense of "The more things change, the more they stay the same" -- middle school was 1977 for me, and the same thing was going on then.
Chip H.
The trend seems to becoming widespread, I guess 10 years and all the old wires are gonna start to be taken down
What about DSL?
Not everyone will have FITL (fiber-to-the-curb), so the existing copper lines will still have a use.
Chip H.
Been that way since early 1983.
Chip H.
It's Al Gore's internet. Did anyone ask him if this was a planned outage?
Chip H.