[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Datashare channels...
- From: Remy Chi Jian Suen <remy.suen@xxxxxxxxx>
- Date: Mon, 20 Apr 2009 15:23:43 -0400
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=c9Rga92YZSBMtgpQj8R4YAn9ssdzwGubUVj5qo0DGWDZzvenmUESRd47Ro5SckeAiJ HrcRsheLl6NcpzZmG+a9QjZNcNGbhgdPxPe/5iJnHtRxhvYiCiXLn+DQNKmvpM56gG0W 0E/RBkIJXerhOzjJgQrTwfJ8JDr7e+HJabDUY=
On Sat, Mar 28, 2009 at 3:01 PM, Scott Lewis <slewis@xxxxxxxxxxxxxxxxx> wrote:
> 1) Use Buddy Classloading (with appropriate one...e.g. dependents, etc).
> 2) Use OSGi's Dynamic-ImportPackage (with wildcard I expect)
> In bundle B.
Wait a minute here. Why does DocShare not need to do this? It can
deserialize XMPPIDs just fine. Am I missing something here?
> So what are you using to implement datashare in this case? Is it nio? Note
> that we've already got a signs of life provider based upon CDO (which is in
> in turn based upon nio)...but the more the merrier, of course.
Since NIO does non-blocking I'm using that at the moment. It would be
nice if it could be replaced by (the presumably superior) CDO