Decision taken it will be:NHibernate.ByteCode.Castle
NHibernate.ByteCode.LinFu
NHibernate.ByteCode.xyz

It is because the real responsibility to provide a ProxyFactoryFactory is of
an implementation of IBytecodeProvider and we can maintain our specific
feature IInjectableProxyFactoryFactory and the same architecture of
Hibernate3.2.

2008/11/7 Fabio Maulo <[EMAIL PROTECTED]>

> well.... we can make the "thing" more easy...We are not sure which name is
> good ?
> Skip that name:
> NHibernate.xxxxDynamicProxy.ProxyFactoryFactory
>
> No?
>
> 2008/11/7 Tuna Toksöz <[EMAIL PROTECTED]>
>
>> ProxyFactories would be my choice
>>
>> But the sad thing is:
>> NHibernate.ProxyFactories.xxxxDynamicProxy.ProxyFactoryFactory  :):):)
>>
>> On Fri, Nov 7, 2008 at 7:13 PM, Fabio Maulo <[EMAIL PROTECTED]> wrote:
>>
>>> ProxyFactories
>>
>>
>>
>>
>> --
>> Tuna Toksöz
>>
>> Typos included to enhance the readers attention!
>>
>
>
>
> --
> Fabio Maulo
>



-- 
Fabio Maulo

Reply via email to