langreiter.com plain, simple: 2002-06-23

LANGREITER.COM plain, simple

START

INDEX

2002-06-23

CREATED BY chris • LAST EDITED BY chris 8217 days AGO

galois.com/~sof/hugs98.net/

2002-06-23-hugsNet

Ein weiterer Gedanke, der sich schön langsam durchzusetzen scheint: Asynchronous Events/Messages are safer and simpler than Explicit Threading in almost all cases.

Holger Kruse: "Of course single-threading and async i/o combined with a state machine per pending task leads to pretty much exactly the same performance (sometimes even better) as multi-threading with blocking i/o per thread. One advantage of the single-threading solution is that load balancing, fairness, resource management, sequencing etc. usually become much easier, because the information required to manage that is explicitly available in the data structures, not hidden within the threading environment. The main drawback is that writing programs that way takes some getting used to."

2002-06-23-asyncEvents

Semant-O-Matic is a search engine for a total of 11 weblogs emplyoing Latent Semantic Analysis (LSA, in my experience, produces slightly amusing general weirdness rather than sensible search results. Of course your definition of 'sensible' may vary).

www.idlewords.com/semantic/

2002-06-23-lsi

"Cognitive Dissonance" — once you've gone to the effort to learn one system, you have a natural tendency to view it as better than alternatives. This holds for automobiles, spouses, and computer algebra systems."

In Richard Fateman: A Review of Mathematica (nota bene: antique)

2002-06-23-mathematicaRev

So what's Palladium?

www.msnbc.com/news/770511.asp

I upgrade my box in order not to be able to burn my MP3s any more? Go fsck you.

2002-06-23-palladium

"Halcyon Days: Interviews with Classic Computer and Video Game Programmers"

www.dadgum.com/halcyon/

2002-06-23-halcyonDays

Et moi, je respire encore aussi.

So what's doc/literal, exactly? "[SOAP, doc/literal style] promotes XML on the wire to a first class citizen, and ditches the concept of language-to-XML mapping." — And I think that's the only sensible thing to do in the SOAP world. SOAP won't ever work in the trouble-free fashion XML-RPC does in an RPC scenario. In a message-centered scenario (where a message flows through a network of processing cells), however, you'll want to use and process arbitrary XML documents anyway, so why spend ages wrestling with de/serialization issues? Of course, it might be rather depressing that essentially all of the SOAP specification (especially Section 5) is utterly irrelevant in this scenario with the exception of the Envelope.

Background reading: