Slashdot Mirror
Google Patents Staple of '70s Mainframe Computing
theodp writes "'The lack of interest, the disdain for history is what makes computing not-quite-a-field,' Alan Kay once lamented. And so it should come as no surprise that the USPTO granted Google a patent Tuesday for the Automatic Deletion of Temporary Files, perhaps unaware that the search giant's claimed invention is essentially a somewhat kludgy variation on file expiration processing, a staple of circa-1970 IBM mainframe computing and subsequent disk management software. From Google's 2013 patent: 'A path name for a file system directory can be "C:temp\12-1-1999\" to indicate that files contained within the file system directory will expire on Dec. 1, 1999.' From Judith Rattenbury's 1971 Introduction to the IBM 360 computer and OS/JCL: 'EXPDT=70365 With this expiration date specified, the data set will not be scratched or overwritten without special operator action until the 365th day of 1970.' Hey, things are new if you've never seen them before!"
This is supposed to be new...
Google Labs is supposedly working on a next-gen programming development environment that allows source code statements to be physically manipulated like a deck of cards.
Cut the foreign born crap (Aussie here). Just say they are incompetent and leave it at that. Its more accurate that way.
It's not like Microsoft was ever going to be interested in that anyway. They must get cents back from the disk manufacturers for perpetuating their ever-growing temp folders.
I don't know whats worse, Google applied for this, or the USPTO approved it.
If you actually read the patent, it is specifically for a similar method, but designed for Distributed File Systems. This is different from just a single file being names a certain way. It is an algorithm based on the location of other related files, each different file's modified and Time to Live (TTL) dates, and the factors determined by the, keywords here, plurality of servers. If they tried to patent a regular temporary file that would be different, but this is a distributed system specifically for a file that is distributed in different parts on different systems. If you still think this has been done before, I would love to see the source for that information and gladly would recant myself given that.
The man who cannot imagine a horse galloping on a tomato is an idiot - Andre Breton
The same thing happened in the 80s and early 90s when microcomputers started gaining features like virtual memory, protected modes, out of order execution, etc... People thought these were all brand new things, when in fact mainframe processors had done all that 20 years prior in the 1960s.
I bet when all the kids were super-excited about programming on the i386 with its "OMG VIRTUAL MEMORY!!!" the older guys who had worked on mainframes just rolled their eyes. :)
Read about the IBM 360/91 if you want details on what I mean. It was amazing when you consider the year it came out.
The summary is wrong. Folks, please stop reading the abstract, and read claim 1 instead.
This is what is patented:
1. A computer-implemented method comprising: selecting a file having a path name in a distributed file system, wherein the file is divided into a plurality of chunks that are distributed among a plurality of servers, wherein each chunk has a modification time indicating when the chunk was last modified, and wherein at least two of the modification times are different; identifying a user profile associated with the file; determining a memory space storage quota usage for the user profile; deriving a file time to live for the file from the path name; determining a weighted file time to live for the file by reducing the file time to live by an offset, where the offset is determined by multiplying the file time to live by a percentage of memory space storage quota used by the user profile; selecting a latest modification time from the modification times of the plurality of chunks; determining that an elapsed time based on the latest modification time is equal to or exceeds the weighted file time to live; and deleting all of the chunks of the file responsive to the determining.
I think it's time for a crowdsourced patent challenge web site run by the USPTO where there would be a period of public comment for each patent about to be awarded in order to help underpaid (and I imagine under-resourced) examiners find Prior Art.
A lot fewer patents might be awarded, but ones that are would be genuinely new -- this might also save the world billions of dollars.
Did you also inspect the quota for the user owning the file to determine if you should delete it? Were the files also stored in a distributed file system, with chunks of the file on separate systems?
Every single claim in that patent mention both of those things.
The naming of files is an example of a part of a claim. To infringe on a patent you need to infringe on at least one entire claim.
Miniaturization took care of that.
Whether or not it could be done for some arbitrary price is not relevant.
Doing something over again in a different medium is still not invention no matter how much you want to shill for companies that would grind you into crackers if given enough motive.
A Pirate and a Puritan look the same on a balance sheet.
find /tmp/* -mtime +14 -exec rm {} \;
"GET / HTTP/1.0" 200 51230 "-" "Mozilla/4.0 (compatible; Setec Astronomy)"
But the USPTO is populated by idiots.
They are deserving of the disdain and ridicule reserved for the Postal Office, Congress, etc.
Which is a shame because I've always figured they had some pretty smart people there. The examiner should have taken a shit on the application and mailed it back with a note saying,"this is what your application is worth".
They are either complete morons or...are getting payoffs. And Google will just use it as club some day on a small outfit that doesn't have half a million dollars to fight a lawsuit.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
It's just another version of a dog licence intended as a petty revenue stream. When a patent is granted that's proof of nothing other than the government is aware of it and has it on file - validity these days is apparently supposed to be sorted out in court and is none of the patent office's business.
The "summary" wholly misrepresents what the patent is about. It's not about having an expiration date in the filename at all. When someone advocating a position lies to me, as this submitter did, I figure the reason they are lying about the issue is because they realize that the truth doesn't support their position.
Rather than choosing an expiration date ahead of time, the patented method deletes a file (or not) based on multiplying the time to live by the inverse of the user's quota usage, plus the latest of several modification times. The patent covers only using that specific algorithm, and only when the TTL is represented within the filename.
Is that algorithm obvious? Several Slashdot commentors who say the are programmers read the explanation of the algorithm and still didn't understand it at all. One might say that if it's explained to you and you don't "get it", it's probably not obvious.