Re: Design Question

From:

Mark Space <markspace@sbcglobal.net>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 02 Sep 2006 19:37:45 GMT

Message-ID:

<d4lKg.14178$1f6.12932@newssvr27.news.prodigy.net>

Zaph0d wrote:

I would choose a different, though more chumbersome, approch, which is
based on seperating as much as possible.

This is good, and very general. I recognize at least some of the ideas
here. However, if the designer/coder doesn't understand why things are
being implemented this way, it may not buy him or her much. Can I ask
what design patterns are being used here? Any good links to a reference
explaining when (and when not) to use this technique?

------code------
interface RecordPersistor{ //not public - package visibility only
  persist(Record record);
}

class RecordDBPersistor implements RecordPersistor {} //for example

public interface Record { //all your data getters/setters }

class RecordImpl implements Record { //package visiblity
  public RecordImpl(RecordPersistor rp){/*saves the rp object*/}
  public persist(){ rp.persist(this);}

I'm curious about persist() here. Is it part of the Record interface,
or do you extend the interface here? (Or, does it matter?)

}

public RecordFactory {
Record createRecord(/*params, persist method*/){ return new
RecordImpl(new RecordDBPersistor());} //for example

This is good. I at least recognize the factory design pattern here.

------code------