The approach I'm referring to is isolating reflection ops into a parser.  
Instead of doing reflection at the edges like this, there would be metadata 
that shows the position and context of the param.  I use this approach un feign 
which has negligible and constant (microsecond) overhead per invocation.  We 
can do something similar in jclouds for spots like this.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/155#issuecomment-25216185

Reply via email to