Fibrillation redux

[John B. Matthews]

Recently, a discussion [1] arose regarding reentrancy in mode-view-
controller (MVC) updates that was likened to fibrillation [2]. Under
the heading "Issues With Application Design" [3], the article "Java SE
Application Design With MVC" [4] addresses the issue and includes an
example using two views attached to a single model.

The article [4] also compares traditional MVC architecture with the more
recent MVP variation.

[1]<http://groups.google.com/group/comp.lang.java.gui/browse_thread/threa
d/17fba1b6116d908>
[2]<http://mindprod.com/jgloss/fibrillation.html>
[3]<http://java.sun.com/developer/technicalArticles/javase/mvc/#5>
[4]<http://java.sun.com/developer/technicalArticles/javase/mvc/>

--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>

[markspace]

John B. Matthews wrote:

> [3]<http://java.sun.com/developer/technicalArticles/javase/mvc/#5>

This is a good find:

"The model notes that the value of the second update matches that of the
first, its current value, and refuses to send a change notification.
This is always a safe programming practice, and it automatically occurs
if you use the PropertyChangeSupport class provided in the java.beans
package. However, it does not keep the model from receiving a redundant
update. "

Good to see someone already fixed this. I like to be able to reuse
someone else's code. :)