A New Protocol For Faster Web Services?

Roland Piquepaille writes "Jonghun Park is an Assistant Professor of Information Sciences and Technology at Pennsylvania State University. He says that a new protocol can improve Web services. Sandeep Junnarkar broke the story. "Jonghun Park proposed a method for sharing information between systems linked on the Internet promises to speed collaborative applications by up to 10 times the current rates. The protocol is based on an algorithm that lets it use parallel instead of serial methods to process requests. Such a method boosts the efficiency of how resources are shared over the Internet. The new protocol is called Order-based Deadlock Prevention Protocol with Parallel Requests." Check this column for some excerpts or read the CNET News.com article for more details. More information about Jonghun Park's works can be found at his homepage."

Comments

Order-based deadlock prevention?

[Anonymous Coward]

Oh, how original.

Anybody who's done real database engineering knows the two points necessary to prevent deadlocks: (of course, most designers/programmers don't do this...)

1. Every process locks resources in the same order.

2. No process ever escalates a lock.

Enforce these two adages ruthlessly and you'll never get a deadlock.

So all this guy is saying is "Engineer your distrubuted databases properly." Woot.

Is this really the job of the protocol?

[CrazyJ020]

"The proposed protocol is free from deadlock and livelock, and seeks to effectively exploit the available alternative resource co-allocation schemes through parallelization of requests for required resources,"

This article is useless. This quote is the only information that is remotely informative in the entire article.

And to get to my point, the management of resource access is hardly the job of the protocol. It is the job of the underlying web Service implementation to deal with these issues. Why should the protocol even have knowledge of the the resource state?

Re:Is this really the job of the protocol?

[GreyPoopon]

Why should the protocol even have knowledge of the the resource state?

I think providing the protocol with this knowledge is supposed to speed up the whole process while still preventing dead/livelock situations. However, as you said, the article is way too barren of any real information to assess how this is really supposed to happen. It may be intentionally devoid of details until the authors of this protocol determine whether or not they really "have something."