Comments for Code by Martin

Comment on Caching Filter Queries with Coherence by Patrick Peralta

Patrick Peralta — Sun, 28 Sep 2008 19:40:45 +0000

Hi Martin,

Great post! I expanded more on this technique here:
http://blackbeanbag.net/wp/2008/09/28/coherence-query-cache-technique/

Comment on Caching Filter Queries with Coherence by ~pperalta » Blog Archive » Coherence query cache technique

~pperalta » Blog Archive » Coherence query cache technique — Sun, 28 Sep 2008 19:38:47 +0000

[...] few days ago I read an excellent post by Martin Elwin on creating a query cache using Coherence. To summarize, he uses a Coherence Filter [...]

Comment on Clustering Scala Actors with Oracle Coherence for Fun and Profit by AMIS Technology blog » Blog Archive » An evening with Oracle Coherence and Oracle Data Integrator - on Compute Grids, JMS implementations and trickle feed

Mon, 01 Sep 2008 09:30:31 +0000

[...] Oliver’s Pimp my Data Grid Ashish’s thoughts: When you let the grid do your jobExample scenario of implementing a parallel job processor with Oracle CoherenceOTN Forum Thread: Coherence Grid as Service Event [...]

Comment on UML Use Case Diagrams & Graphviz by Stephan Eggermont

Stephan Eggermont — Wed, 06 Aug 2008 13:34:26 +0000

Hello Martin,

Nice description. Graphical tools are really not very nice for working with large requirements sets.
Keeping the documentation up-to-date becomes a nightmare. I much prefer the smalltalk squeak toolset.
I already generate class diagrams at package- and system level from descriptions in the source
code (Magritte), and integrate them in LaTeX docs, and will add use case diagrams.

Stephan

Comment on Scala XML and Java DOM by pligg.com

pligg.com — Tue, 15 Jul 2008 10:50:59 +0000

Scala XML si Java DOM…

Cum treci de la DOM to Scala XML in cel mai eficient fel?…

Comment on Clustering Scala Actors with Oracle Coherence for Fun and Profit by Martin

Martin — Mon, 14 Jul 2008 13:44:08 +0000

Kirk,

Thanks for your comment about Terracotta - just a question:

You’re saying “that all cache/clustered products have”, but I’m not aware of any specific single points of failure in Coherence using the standard configuration. Failure of any single cache node should not matter, considering there’s no central instance (like in a hub/spoke model) but rather all participating instances are peers and data always exist in more than one node at any point in time.

Did you have a certain failure mode in mind that includes Coherence as well as Terracotta?

Kindly,

Comment on Clustering Scala Actors with Oracle Coherence for Fun and Profit by Kirk

Kirk — Mon, 14 Jul 2008 06:36:18 +0000

Hi Martin,

Nice bit. I should point out that Terracotta has the same single point of failure that all cache/clustered products have when setup using default configurations.

Regards,
Kirk

Comment on Clustering Scala Actors with Oracle Coherence for Fun and Profit by Oracle Coherence and Scala « Brian Oliver

Oracle Coherence and Scala « Brian Oliver — Sun, 13 Jul 2008 15:53:15 +0000

[...] While I don’t really have any experience with Scala, (yet it was nice to see this article by Martin Elwin. Perhaps next weekend I’ll have some time to play around [...]

Comment on Scala XML and Java DOM by Martin

Martin — Wed, 02 Jul 2008 09:35:03 +0000

Thanks, Burak!

It turned out I didn’t need the Scala XML->DOM transform, but I’ll take a look at the NodeTraverser - good suggestion.

Comment on Scala XML and Java DOM by Burak

Burak — Tue, 01 Jul 2008 20:09:34 +0000

Hi Martin, way to go!

Don’t worry, the SAX factory adapter is not going to go away. I find it you are using this library class in exactly the way it is supposed to be used.

About implementing the DOM API by wrapping Scala XML, it could work as long as you don’t mutate anything. About option 2, there is already something that generates events, it is feasible to get SAX events with a bit of adapting I guess … http://lampsvn.epfl.ch/trac/scala/browser/scala/tags/R_2_7_1_final/src/library/scala/xml/NodeTraverser.scala?view=markup