James,
Thank you for the clarification. That does in
fact help. While I think more about what you wrote,
I'd like to ask a couple of other questions:
1) To what extent would the changes you're proposing
affect the current APIs? You mentioned the proxy
pattern in an earlier message. So I assume the answer
is the APIs wouldn't change. Then again, you're
talking about making certain parts of the code
transport agnostic (which, incidentally, I agree
with). So I'm left to wonder if that would
necessitate a change to some of the APIs. Also, are
you thinking about a separate package structure for
some of your classes?
2) Would any of the changes you're proposing improve
the code with respect to caching? The EAR file I
deploy contains both slide.war (for WebDAV clients)
and EJBs that use Slide's low-level APIs. What I've
observed is that changes made through the EJBs are not
immediately available to WebDAV clients, presumably
because the Slide servlet caches information. I've
been reluctant to disable caching in the servlet for
fear of impacting performance. But I was wondering if
a centrally-accessible Slide kernel might solve this
problem.
Thanks much,
-kevin
--- James Higginbotham
<[EMAIL PROTECTED]> wrote:
<snip/>
>
> Does this all make sense and clear up some of your
> questions/issues
> better?
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
