Great idea! Something like this would work great for me, core - The code that handles signing. This package should have no dependencies at all. JRE should provide everything. consumer - The HttpClient interface. provider - A reference implementation of provider. This is as good as an example. It's impractical to provide real server functions in the library. As a provider, you have to face many tough issues, like how to store consumer info/token, how to check nonce etc.
Thanks! Zhihong On Apr 15, 11:16 am, John Kristian <jmkrist...@gmail.com> wrote: > To minimize dependencies, I recommend removing Java packages that you > don't need. You can eliminate several dependencies this way, such as > the Java Servlet API and both Apache HTTP client libraries. > > I'm thinking of moving parts of oauth-core into new modules; for > example a module for consumers (clients) and another for service > providers (servers). Would that be helpful? Are there other parts > that you'd like to be in separate modules? > > On Apr 15, 7:45 am, Zhihong <zhih...@gmail.com> wrote: > > > The OAuth lib itself builds fine but sometimes we embed OAuth library > > in other JARs. The build error occurs in a JMeter plugin for OAuth. We > > build the plugin with OAuth code so only one JAR is delivered. For use- > > cases like this, it's very important to keep the dependencies to a > > minimum. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
