Apple Patent Claim Threatens To Block Or Delay W3C 332
Kelson writes "The W3C Widget specification is running into a problem: Apple claims a patent on automatic updates and is unwilling to license it royalty-free in the event that it impacts the spec. The W3C is investigating to determine whether the spec includes anything covered by the patent, and decide what to do."
Use of this patent against web browsers? (Score:3, Interesting)
If you read this claim, it seems that any webpage loaded through a caching web-browser *could* fall under it.
1. A method for automatically updating software programs on a computer, comprising the steps, of:
storing an updated version of a program at a designated location in a remote memory that is accessible to the computer;
Being that most browsers will check a cache to see if it already has your content, the act of overwriting the cache before loading the asset for your page seems to run afoul of this auto-update process.
Bunch of hypocrites (Score:4, Interesting)
I assume Apple doesn't get to sit in? (Score:5, Interesting)
According to the Patent Advisory Group [w3.org] they've formed to deal with this hurdle, the PAG membership includes "Advisory Committee Representatives of each Member participating in the Web Applications Working Group".
Of course, the Web Applications Working Group [w3.org] includes: "Apple, Inc. (4 representatives)".
Isn't it kind of a conflict of interest for Apple to be sitting on the committee that has the purview to:
?
Re:without interruption of its primary function... (Score:5, Interesting)
Yeah, I'm a grumpy old man...what of it...
Re:You missed the transparent part. (Score:3, Interesting)
Updating a running program without interruption is everything but trivial.
It can be pretty easy. I helped write a database app where every time the menu form was invoked, it would check the back-end database to see what the "current" version of the front-end should be. If it wasn't the same, it would launch the new version and quietly kill itself.
The user only experiences a slight delay that can not be differentiated from network congestion or heavy database load.
The key here is that the app does the work of checking for updates at an easy time to do it (user is transitioning from one form to another) and not based on an external stimulus (an interrupt).
Doing this for something like a word processor or spreadsheet that doesn't have such stark transitions would be trickier since it would have to somehow save the state, reload itself, and restore the state.
I think in the case of the patent, they're talking about updating the app during a page-load, so the user won't notice the delay because they're going through a state-change already. I may be mistaken, but I do not think the app gets updated in the middle of reading a page without doing a refresh of some kind.
Re:without interruption of its primary function... (Score:3, Interesting)
Re:I call shenanigans! (Score:4, Interesting)
What's funny is that the steps that you've outlined seem to describe exactly how Microsoft's ClickOnce [wikipedia.org] works when it comes to updates. So if Apple threatens to sue, it would seem that there is at least one large player interested in opposing them on this.
I can give a example from OS X (Score:3, Interesting)
Someone from Apple scene does use that concept. Intego Netupdate. It has a preference to automatically install and reboot after updates, without even asking to user. Thank God, it is disabled by default.
In fact, it performs exactly the way patent says. You may even be greeted by "Enter serial number you purchased while you upgrade your software" message.
Apple being victim of their stupid lawyers as usual, not even surprised. They should separate RIAA/MPAA iTunes types from the Technical types.
What if MS steals their concept as usual and implements like its own? Well, it has been solved by Real Networks for their million dollar patents. Free to GPL, patented for closed source. As people here busy with "buffering" jokes and spyware allegations regarding their free/open source software, I better remind it.