doflo-dfa

still a work in progress but should be soft launching in the next month or two

We have been using the following pattern after split control approach (after admittedly trying a number of other apollo wrapper approaches .... this has proven by far the most predictable...

I may have accidentally left out the promise helper we are using inplace of the generic Promise.resolve() ... cause I am dumb ill post a better example

> > This will peg the CPU at 100% while any queries are loading. Not the way I was originally doing it but ... what do you think about this...

I totally appreciate that... and appreciate the comment ... we are rapidly working through at least having a solution that is workable as we try to release something that doesn't...

@pedroigor ... I was curious what's the right way to do this ? ... why is going from a confidential client to a public client generically bad ? I mean...

So is the thought that eventually the keycloak-JS project would have some type of a BFF proxy project as a companion ? I only bring it up to make sure...

Understood .. and honestly as long as there are guardrails anything implemented would have to be more secure than some of the other workaround solutions that are being proposed... Even...

I think the most common use case is simply one of conferring identity ... I mean moving from confidential to public that is all I would assume ... for that...

This is a very hacky solution but ... it does solve the issues caused by this on modern browsers which should solve for 90% of our applications users ... I...