All.,

We discussing in the CWG meeting earlier today and the conclusion was to omit 
the non-XML bindings.  Jorge will be refactoring his commit (after abandoning 
it) to include only the non-XML and will provide a different gerrit item with 
the non-XML for future reference (i.e. it too will be abandoned with comments 
along the lines of it being there for reference should there be a desire to add 
that functionality to the Obj-C binding down the line.

George,  does only delivering the XML reduce the risk of the work not 
completing by next week? That was one of the rationales for omitting that from 
the API for 16.10).

From: [email protected] 
[mailto:[email protected]] On Behalf Of George Tang
Sent: Tuesday, September 06, 2016 7:16 PM
To: Josh Spain <[email protected]>
Cc: [email protected]
Subject: Re: [Allseen-core] Non-XML vs XML APIs for Security 2.0

Hi,

I'm working on the Java bindings for security 2.0. Currently, there is a commit 
for the SecurityApplication interface. This commit includes 
PermisisonConfigurator and the SecurityApplicationProxy. There were some 
dependencies that I didn't want to spend time on different commits.

https://git.allseenalliance.org/gerrit/#/c/8757/8

The majority of securityapplicationproxy is implemented, and some of 
PermissionConfigurator is implemented. There is some risk of not getting this 
done by next week, but I am committed to finishing this before the deadline.

George

On Tue, Sep 6, 2016 at 7:02 PM, Josh Spain 
<[email protected]<mailto:[email protected]>> wrote:
Core Team,

We have internally reviewed the Non-XML vs. the XML APIs for Security 2.0 in 
C++, Objective-C, and Java.

For all three languages the Non-XML bindings are much more natural to the 
programmer. However, the XML bindings could also potentially be useful.

Here is the current implementation status:
Language

Non-XML

XML

C++

Implemented

Implemented

Objective-C

Implemented

Implemented

Java

In Progress

In Progress


I believe many of these have been pushed and reviewed, but I'm not certain of 
the merge status.

@Affinegy team, anyone who has any more updates on this please speak up.

Thanks,
Josh
[https://s3.amazonaws.com/ucwebapp.wisestamp.com/12898986-6b24-4785-b392-dfd3cd5cdd09/Affinegylogo201450px.format_png.resize_200x.png]

Josh Spain
Director of Engineering Affinegy, Inc.
t.512-535-1700 x1006<tel:512-535-1700%20x1006>
a. 1705 S Capital of Texas Hwy, Suite 310, Austin, TX 78746 USA
Website<http://affinegy.com>

Email<mailto:[email protected]>
[https://s3.amazonaws.com/images.wisestamp.com/icons_for_colors_32/linkedin.png]<http://www.linkedin.com/in/joshspain>

 
[https://s3.amazonaws.com/images.wisestamp.com/icons_for_colors_32/twitter.png] 
<http://twitter.com/affinegy>


[https://s3.amazonaws.com/images.wisestamp.com/icons/twitter.png]Latest 
Tweet:<https://twitter.com/Affinegy>

Texas is it. Realy. Check out 11 Reasons Why Everyone Wants to Move to Texas - 
U.S. Global Investors, https://t.co/3Q3pt3dSlv ( 
#USFunds<https://twitter.com/USFunds>

)

Read More<https://twitter.com/Affinegy/statuses/772149067178647552>


[https://s3.amazonaws.com/images.wisestamp.com/email-apps/twitter_button/twitter-white.png]<https://twitter.com/Affinegy>


_______________________________________________
Allseen-core mailing list
[email protected]<mailto:[email protected]>
https://lists.allseenalliance.org/mailman/listinfo/allseen-core

_______________________________________________
Allseen-core mailing list
[email protected]
https://lists.allseenalliance.org/mailman/listinfo/allseen-core

Reply via email to