[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [zzdev] ***ATTENTION*** (was: [Gzigzag-commits] gzigzag/src/impl SimpleSpace.java TransientTextScroll.java)
- Subject: Re: [zzdev] ***ATTENTION*** (was: [Gzigzag-commits] gzigzag/src/impl SimpleSpace.java TransientTextScroll.java)
- From: "B. Fallenstein" <b.fallenstein@xxxxxx>
- Date: Thu, 07 Feb 2002 11:50:13 +0100
- Cc: ZZ Development <zzdev@xxxxxxxxxx>
- References: <E16YdmB-00028W-00@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <3C62346B.CEBE24B1@xxxxxx> <20020207095732.GB20609@xxxxxxxxxxxxxxxx>
Tuomas Lukka wrote:
> On Thu, Feb 07, 2002 at 09:01:46AM +0100, B. Fallenstein wrote:
> > Tuukka Hastrup wrote:
> > > Log Message:
> > > Multiplexing now saves changes back to the pool the data was from
> > ATTENTION: Are you sure that the tests still write to the transient and
> > not the permanent pool? Otherwise, you will soon have *LOTS* of junk in
> > your permanent pool!
> We have to make a different mediaserver, "TransientTestingMediaServer" or
> such to do that now.
I don't understand. Why duplicate code into a hack instead of doing it
correctly (lift MultiplexingMediaserver to the next level: give it
intelligence about which pools it may save into and which it may not)?
Or do you think we should have another CacheMediaserver (because if you
edit a space from the cache you do not want your modifications be
written in the cache), a WebMediaserver (because if you edit a space
downloaded from the web, you *cannot* write your modifications on the
read-only HTTP server), and so on? The point of MultiplexingMediaserver
is to solve a general problem instead of solving the same problem over
and over again (when it was written, the problem at hand was that the
tests needed a transient mediaserver, but it's also been used for
public/private pool separation, to use the public HTTP repository for
loading the space but saving to a local disk, etc.).