[MUD-Dev] World Persistence, flat files v/s DB v/s ??

[Vadim Tkachenko]

Matt Chatterley wrote:
> 
> On Tue, 24 Mar 1998, Vadim Tkachenko wrote:
> > Matt Chatterley wrote:
> > >
> > > On Sun, 22 Mar 1998, Chris Gray wrote:
> > > > [Ben Greear:]
> 
> [Snip]
> 
> > > It is my understanding that (at least, according to the 1.1.x
> > > specifications), a Thread is terminated when its stop() method is called.
> > > Of course, some Java implementations may be buggy. :)
> >
> > Surprisingly, they are :-))
> >
> > Some things worth mentioning:
> 
> What a shocker. My opinions (and an attempt to tickle this back to full
> mud relevancy):
> 
> > JDK 1.0.2: Thread.interrupt() doesn't work. Thread.stop() doesn't work
> > as expected if called from within the thread you want to stop.
> 
> 1.0.2 is very out of date, though (and in general was buggy).

The reason I mentioned it here is that the big companies still have the
JDK 1.0.2 their APPROVED implementation, however stupid  that sounds...

> You should
> be using at least 1.1.3v2 nowadays, 1.1.5 or JFC (I think thats the name
> for 1.2) even.

It's not quite clear what they mean by JFC, but for sure it contains
what used to be Swing, which is the AWT extension, plus modified
container library.

> > Netscape Enterprise 3.* JVM: the same. BEWARE: it advertises itself as
> > JDK 1.1 compliant, but in fact hopelessly broken - apparently, these are
> > not the only things which don't work - my package which had been tested
> > on JDK 1.0.2 from different vendors for almost two years choke and died
> > at once.
> 
> Blech. The only browser I trust for proper Java compliance is HotJava.
> Netscape 3.X needs patching to work at all properly, I think - and
> Netscape 4.X is just bloated.

PLEASE slow down. Enterprise is not a browser, it's a server. You gonna
develop the Java server, especially commercial quality one - you gonna
hit that sooner or later. Keyword to the solution is ServletExec.

> > JDK 1.2: Thread.stop() is deprecated - and let it rest in peace,
> > Thread.interrupt() is quite enough.
> 
> Hmm. So threads truly are never destroyed by stop - really just stopped
> and left useless? If so, interrupt() is certainly a better method. :) This
> is something Java-in-a-Nutshell is not explicitly clear on.

And, usual method of handling InterruptedException so far used to be

catch ( InterruptedException ex )
{
}

so review your code :-)

>         -Matt Chatterley

--
Still alive and smile stays on,
Vadim Tkachenko <vt at freehold.crocodile.org>
--
UNIX _is_ user friendly, he's just very picky about who his friends are