Kees Jongenburger wrote:
> >   - Which taglib jar must be shipped? (one provides all features, but
> >     doesn't work in tomcat 4, the other one is more conservative). More
> >     or less it was decided to ignore tomcat 4 compatibility. Still that
> >     needs to be arranged in the build.
> I would go for the advanced one, I would also like us to have the best
> support for java 1.5
> by including xerces and ecluding the collections backport.

I think we cannot before 1.8 decide to switch to java 1.5. We ship
xerces only 'commented out'. We have no 'collections' backport. We do
have a 'concurrency' backport. This backport runs on java 1.5 itself too
(other packages names), but indeed is used in anticipation of java
1.5. I'd propose dropping 1.4 support for mmbase 1.9. Then the things
you propose can be done to the full extend.

> >   - Must rmmci be installed in the distro? I think the RMMCI package, does
> >     contrary to other packages not contain a directory.
> Perhaps I can write a webstart app so that rmmci is actualy used somewhere?

I myself am quite neutral to shipping rmmci in the distro. Perhaps we
should because we used to do so in previous releases. 

> Its a shame I did not spend much time with mmbase 1.8
> perhaps its enough if people that already use it state there comments
> -did you create new data types?

I did :-)

> -did you migrate from mmbase 1.7

Yes. We migrated for example the quite heavily visited site 'kassa'.

> -have you ruun mmbase 1.8 clustered?

Yes. Teleac is running an 1.8 site, clustered together with a bunch of
1.7 installations.


> > - CommandServer for image-magick. Using this would avoid the problems
> >   arising from the fork done by the JVM for the Runtime.exec.
> is that a small mmbase server?

It will not contain mmbase. Just listening on a socket (or stdin for
use with xinetd) for things which are to be fed to image magick. The
mmbase side needs a small adaption to be able to connect to that. It is
quite straight-forward, it just is a bit tricky because I need to get
the PipedInputStream stuff and so on right. So, all in all it will not
be much code, but quite useful, because one could assign more liberaly
memory to ones JVM then.

Michiel


-- 
Michiel Meeuwissen                  mihxil'
Peperbus 111 MediaPark H'sum          [] ()
+31 (0)35 6772979         nl_NL eo_XX en_US



_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to