<mentor>Are you sure you want to continue this discussion with a vote at this point? It's OK to have votes about anything you want :-) but.... they tend to be polarizing and end up with a losing side who may not be happy. I think that trying to get a consensus on design decisions through discussion is often a better route.</mentor>
<interested party> I don't understand the details of this proposal. Could someone come up with a realistic example showing how the "same" OAuth message would be sent using annotations, and not using annotations, and what would happen internally to this information? It might be obvious to anyone who knows anything about oauth but would help me out a lot </interested party> thanks david jencks On Jun 25, 2010, at 7:55 AM, Simone Tripodi wrote: > Hi all, > I'm here to call a new vote to define our design direction. Some > threads ago on this ML, Pid and I were discussing about the use, or > not, of Java metadata Annotations to enhance OAuth messages and > tokens. > > Pros: > * marshallers/unmarshallers to/from strings could be auto-generated > using the APT; > * the calculation of the base string (just an example) is parameter agnostic. > > Cons: > * not so hard writing parsers (JavaCC? AntLR? XText?) and serializers; > * not so hard writing the base string algorithm > > So please cast your votes in favor of > > [] Pro Annotations > [] Cons Annotations > > The vote will stay open for the next 72 hours. It would be nice if the > choice comes with a justification, so everybody can take care about > someone else's considerations. > > My vote if > > [X] Pro Annotations > > I already implemented the base string calculus based only on metadata > discovery and I didn't take care about the parameter retrieving > criteria. I'd love to have a choice to see Annotations in action on > compile-time :P > > Cheers, have a nice weekend, > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/
