On Fri, Jul 26, 2013 at 9:36 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Well we can discuss it in another thread but basically commons spirit for > me is more basic and shouldn't be a facade (excepted logging). So i'd > rather see proxy as an implementation of proxying using asm efficiently. > The issue with proxying is not its lifecycle or API in general but its > specificities (cache, proxy names, handlers...). The best solution IMO is > to propose a unified solution which could be a facade but facade means all > impl specificities in its API which makes it harder or specific (in v1 > instantiating the factory was a pain IMO since it is specific). ATM the > question for me is always which one do i import depending my container, do > i test against all proxies impl? Etc... it makes libs hard to write and > maintain
Great feedback! Please start another thread so we can discuss. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
