Gregg Wonderly wrote: > > One of the predominate design problems with HTTP URLs is the complexity > of sent > content vs URI indicated values. So, many people do build entire web > applications treating GET like POST because they can indicate in the URI > everything that they would otherwise have to tack onto PUT or POST with > content > that is more verbose or more work to manage on both ends.
Two former colleague of mine spent well over a week running down a bug that was causing a transactional publishing to abort. The problem: obj.getTitle() had a side effect of updating an index, which in turn interfered with the publishing transaction. A 2 line patch solved it. So I don't think is a problem unique to HTTP. SQL does come to mind as a language where methods mean exactly what they say they mean. cheers Bill
