[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [zzdev] Re: [zzdev] ***ATTENTION*** (was: [Gzigzag-commits] gzigzag/src/impl SimpleSpace.java TransientTextScroll.java)
- To: "B. Fallenstein" <b.fallenstein@xxxxxx>
- Subject: Re: [zzdev] Re: [zzdev] ***ATTENTION*** (was: [Gzigzag-commits] gzigzag/src/impl SimpleSpace.java TransientTextScroll.java)
- From: Tuukka Hastrup <Tuukka.Hastrup@xxxxxx>
- Date: Thu, 7 Feb 2002 13:13:38 +0200 (EET)
- Cc: ZZ Development <zzdev@xxxxxxxxxx>
- In-reply-to: <3C625BE5.16072CD4@xxxxxx>
On Thu, 7 Feb 2002, B. Fallenstein wrote:
> 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!
Sorry, I didn't realize MultiplexingMediaserver was in use somewhere
because it didn't work. Now I see we could because the problem was only
> > We have to make a different mediaserver, "TransientTestingMediaServer" or
> > such to do that now.
Here we could copy the old MultiplexingMediaserver for 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)?
We have had the CVS version too long in unusable state - for everyone
except our research group. It is a hack but doing it the right way takes
some time and can easily be done later.
> 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.).
At the moment I see it being used in TestImpl, Client and NileDocument.
For the Client it works to the extent I've tested it. For TestImpl the
hack works. How should it work in NileDocument?
When we are to do multiplexing the right way, we should have it specified
-- Trying to catch me? Just follow up my Electric Fingerprints
-- To help you: Tuukka.Hastrup@xxxxxx