On 24/09/12 19:07, Daniel Kulp wrote:
On Sep 24, 2012, at 8:31 AM, Sergey Beryozkin wrote:
I went ahead and populated AsyncInvoker, as well as added another shortcut
directly to WebClient, to support an async post call.
Dan, have a look please,
That all looks great. Thanks for filling in
Support for wauth and whr is supported as a callbackhandler in the fediz plugin
for the relying party (application). Also metadata support is provided in the
plugin. It's not yet supported for the fediz idp.
--
Oliver Wulff
Blog: http://owulff.blogspot.com
Solution Architect
http://coders
I understand what you mean. The reason why I'd like to have to branches is to
be able to provide a bug fix release even we are working on new features in
parallel.
Backporting fixes from trunk to 1.0.x-fixes branch should be fairly easy with
git cherry-pick but I agree it's more effort.
Thanks
On Sep 24, 2012, at 8:31 AM, Sergey Beryozkin wrote:
> I went ahead and populated AsyncInvoker, as well as added another shortcut
> directly to WebClient, to support an async post call.
>
> Dan, have a look please,
That all looks great. Thanks for filling in all the other methods. :-)
Dan
October is just a week away which would represent 6 months since 2.6.0 was
released. We have several new features now implemented (although I admit I
need to spend some time documenting some of them this week) that would be good
to get out into the hands of the users.Thus, I'm thinking ab
I went ahead and populated AsyncInvoker, as well as added another
shortcut directly to WebClient, to support an async post call.
Dan, have a look please,
One thing that I can have a look later is making sure the retry calls
work in case of async call failures, plus add few more minor
enhancem