Re: status of nio version

You could put everything inside the org.jawin package, and maybe follow the
naming convention already used by IUnknown and UnknownPtr, i.e.:
  - org.jawin.DispatchPtr implements org.jawin.IDispatch
  - org.jawin.COMPtr implements org.jawin.ICOM
  - ...
This is just a suggestion. Since you are doing all the hard work, please
choose whatever you like best.

Regards,

-- Christophe


-----Original Message-----
From: Discussion of Java/Win32/COM integration with Jawin
[mailto:[email protected]] On Behalf Of Roger I Martin PhD
Sent: Monday, June 06, 2005 12:23 PM
To: [email protected]
Subject: Re: status of nio version

Thanks Christophe,

A set of interfaces will be added.  Possibly for the current as well as
the new nio based marshaling.  I'm not big on having xxxxxImpl (which
would require current class names be changed) all over the place.  What
would be another acceptable way? Put the interface in one deeper folder
as in org.jawin.interface.IDispatch or org.jawin.IDispatchInterface?

I'm out for two days,

Roger

Christophe Warland (FRSGlobal) wrote:

>Sounds nice, thank you for be willing to do all that work!
>
>One extra refactoring feature I'd like to ask for is to make it so that all
>methods in COMPtr and DispatchPtr are declared in a separate interface that
>would be implemented by instances of those classes. It would allow me to
>develop some nifty Java Dynamic Proxies on top of. Today, I have to do some
>advance java.reflect tricks to do what regular proxies could do out of the
>box with interfaces.
>
>Thanks!
>
>-- Christophe
>
>
>
>