Just Shelley

For Hire

Recovered from the Wayback Machine.

For hire:

Edgy, quick tempered, slightly manic technology architect/writer. Known to disagree with people on occasion. Can be somewhat opinionated.

Likes music. Orange.

For particulars, enquire within.


UDDI is not the approach

Recovered from the Wayback Machine.

Thanks to TX Meryl, I found this article describing web services in clear, comprehensible terms.

I like the article, but UDDI is NOT the approach to take for web services discovery. Not! Not! Not! Not!

Create a beautiful distributed technology, and then capture it and constrain it by a centralized discovery service operated by big companies. I don’t care if UDDI can be mirrored — that’s not the point!

Think about the technology Google uses to find all the information that we’ve become dependent on. Think about how well the company processes it and packages it and delivers it. I can find anything on the web, thanks to Google.

This exact same type of functionality can be used to discover web services if we implement a few (few, mind you) common specifications. We Don’t Need UDDI. The web of discovery will work for web services as it works for weblogging as it works for Google.

I will continue to beat you about the head on this issue until you ultimately bow to my superior knowledge on this subject 😉

JavaScript Web

Programming the web

Recovered from the Wayback Machine.

Dave is still talking about web versus C programming language. He mentions that scripting is what holds the web together.

Dave, someone has to write the base. You can’t create full applications with Javascript, without something taking the script and translating it into machine understandable bits. And that translation is accomplished through programming languages such as C.

As with proprietary and open source code, scripting and programming with a language such as C are not exclusive – they’re complimentary.

Now, if you’re saying that providing scripting capability gives people who aren’t programmers a chance to have a control over their content, I agree 100%. This is a win/win for both the scripting users and the professional developers — the former has more control over their environment, the latter can focus on the larger and more complex tasks we thrive on. And, yes, we have this increased flexibility due to the web … and to browsers that are enablers.

Perhaps Dave and I do agree on this issue but say things — or read things — differently.