Hi James,

> I agree, I don't want to get too crazy, upset the 
> maintainers, and cause
> a fork.. But, here are my thoughts:
> 
> 1) That JSR's API should be a candidate for the general Slide 
> API to be
> accessed via JMX, EJB, intraVM, etc. 

Mhm. Maybe it could be added a little bit later as
http://mondrian.sourceforge.net/ did it with the JLOAP JSR.

> 2) My understanding, based on talking with the lead on the 
> JSR, is that
> no one has signed up for writing a webdav impl, but that slide will be
> adapting their webdav client to support it.. Not sure if the 
> kernel will
> be refactored to support the same thing
> 3) I'd expect that if we went down the path I proposed, that we'd
> concentrate on the JMX/EJB/VM implementation first, since the webdav
> client is pretty stable and easy to use as is

I agree with your suggestions. The Content API should be desinged that is
independet from the wire protocol. So maybe JXTA support could be added too.
For the Content API we should offer Avalon support as well.

For the WebDAV client I suggest support of NIO as well. NIO and JDK 1.4+
would be a choice if you have to deal with large files and need a valuable
performance. This works well currently with Servlets donwload/uploads, so my
not with WebDav?

> 
> Again, just throwing out my own ideas after working with 
> Slide for a few
> months, in hopes of making it as top quality as the rest of 
> the Jakarta
> projects. I wouldn't rank Slide with misc SF projects, but I would say
> that it ranks low in Apache's project list, esp under the Jakarta
> banner. I hope it gets better, as I think it has a lot of 
> potential and
> there is definitely a gap in the market right now.. You go from silly
> script kiddie implementations in Java to Slide to Tamino ($$ but with
> lots of extras and support). 

Some folks I talked to share your view of the Slide. Maybe I guess a better
documentation would be start. Then a refactored release would be fine. I
would love it to add some support.

Bye
Toby



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to