my web-site; muscle maximizer

Anyhow keep up the good work.
Thanks!

when will you finally understand something about SOA and BPM? Distributed computing is not about some piece of code having the ability to call some other piece of code. It is not about distributed objects vs static methods. Distributing objects has been tried countless times. That will never work. The problem is the semantics of monolithic synchronous runtimes such as OO. Trying to make a distributed call local is the problem, not the solution. Yet, you and so many other always come back there.

You need to create a distributed programming model from scratch, independent of the runtime in which some of the components are implemented. You will actually then understand the need for bi-directional interfaces, orchestration languages, forwards versioning and assemblies. Maybe, just maybe the “unit of assembly” may not the “object”, maybe, just maybe, it could be something else? don’t you think we tried enough times? What’s important is to be able to “assemble” software components that were built by different people at different time using different technologies. It does not matter if it is an object, a static method or a service component?

Stephano:

thank you for having the courage to not be a “follower” of the “good thinkers” of our industry.

JJ-

The other Problem is the BADFINGERS-Problem. There is one person of a thousend persons whos fingers have no or not enough scannable features…that means if your company has 1000 employes, it is likely that one of your employes could not identify himself by fingerprint…..will never open the biometric secured door or activate the PC…

1. Chrome OS is built by a company that practically defined the Internet as we know it today
2. Open Source
3. It’s getting to the point where you hardly need a desktop OS outside of the browser.
4. Software already exists for it in the form of Google Docs for office support, Gmail for e-mail support and millions of other Web-based applications that already run in browsers (including Yahoo mail and other Google competitors)
   Well, I am not that keen on this point, as I think that Chrome and Chrome OS will also redefine the way traditional web applications are built and delivered….
5. Boot time
6. Think of the innovation: The OS will be built to support the browser. Web applications could detect whether they’re running on the Chrome OS and take advantage of what are likely to be some pretty cool features that won’t be found in a browser running on other operating systems. (We can hope, anyway.)
   See my comment on #4
7. Google says Chrome OS will run on multiple platforms, including mobile operating systems.
8. Speed
9. Even though it’s going to be Linux-based, real innovation comes from tossing out what you know and building something new.
10. It’s about time we saw a brand-new OS that’s built for the Web—not the other way around. Sounds like a round peg in a round hole—finally!
    Makes a lot of sense !

Very good point.

Ciao, Diego

Best,
Dave

The thing is we are, we do it daily but the browser we know it right now is evolving to the next piece, whatever that looks like. All major software companies get this and it’s why concepts like “SOA” or “SaaS” exist, as they hint in this direction.

What the end agent looks like who really knows – but i think the internet explorers, firefoxs, operas etc aren’t the right fit.

Scott Barnes
Developer Evangelist
Microsoft.
(MossyBlog.com)

Ciao, Diego

A good analogy for SOAP is only ever calling static methods, and passing arguments around to tell the static method which instance you actually ment to call, if you could.

So I’m confused when you say REST is the counter intuitive one.

This is a good summary of the current state of Internet applications.

I think that the way forward is Lisp running in the browser on top of Flash or WPF. There are some examples on my site.

Cheers,
– Peter Fisk