El vie, 20-10-2017 a las 13:30 -0700, Alex Christensen escribió:
> Right now we have an API::LoaderClient, API::PolicyClient and an
> API::NavigationClient. We intend to remove the first two in the
> future in favor of the API::NavigationClient. I have been working to
> add calls to the
I’m not sure I understand your concern. Deciding policies is definitely part
of navigation. Why would it be important to have the clients be separate
objects?
> On Oct 22, 2017, at 9:22 AM, Alfonso Guerra wrote:
>
>
>
> On Oct 20, 2017 4:30 PM, "Alex Christensen"
On Oct 20, 2017 4:30 PM, "Alex Christensen" wrote:
Right now we have an API::LoaderClient, API::PolicyClient and an
API::NavigationClient. We intend to remove the first two in the future in
favor of the API::NavigationClient.
Is there a semantic model this design
Also, the authentication challenge API also needs redesigning. Right now you
get an AuthenticationChallenge from which you get an
AuthenticationDecisionListener to respond to. Could these become one object in
the GTK API? The current design is based somewhat on the
On Fri, Oct 20, 2017 at 3:30 PM, Alex Christensen
wrote:
Right now we have an API::LoaderClient, API::PolicyClient and an
API::NavigationClient. We intend to remove the first two in the
future in favor of the API::NavigationClient. I have been working to
add calls to
5 matches
Mail list logo