Idea: remove dependence on VF Remoting javascript about ngforce HOT 6 CLOSED

if you know the how, I’d love to do it!
-- 
Kevin Poorman
Sent with Airmail

From: chasd00 [email protected]
Reply: noeticpenguin/ngForce [email protected]>
Date: August 20, 2014 at 10:05:24 AM
To: noeticpenguin/ngForce [email protected]>
Subject:  [ngForce] Idea: remove dependence on VF Remoting javascript (#22)

I looked a little bit into VF Remoting, it's basically just EXTJS. Do you think it's worth the effort to remove VF Remoting and go with straight Angular $http? Regular Angular $http opens the door for interceptors and all the other Angular features when making calls back to SFDC. It also means we no longer have to include the VF component to get VfRemote.js included.

—
Reply to this email directly or view it on GitHub.

from ngforce.

I may have some free time coming up in the next few weeks, i'll check it out when I can.

from ngforce.

I believe the VF component is still required. It injects essential info - stuff we can't just figure out. Stuff like a CSRF token and a Visualforce page Id. Each VFR action, like MyPage.methodName, has a different CSRF. Do you know a different way to get this info?

But, yeah, if you can accept keeping the VF component in, we can set up an API alternative to the Visualforce.remoting.Manager interface. Is that still acceptable?

from ngforce.

Sorry guys, I've been absolutely swamped at work. Yeah, it looks more complicated than I initially thought. I'll keep it in mind but right now it doesn't seem worth the effort.

from ngforce.

Chas, it's not possible to remove the dependency on the component. It
injects a security token kinda thing into the page which is required by the
visualforce remoting web service.

If all you want is to send it through the $http service, I've got a working
implementation of that.

Sorry guys, I've been absolutely swamped at work. Yeah, it looks more
complicated than I initially thought. I'll keep it in mind but it doesn't
seem worth the effort required to just remove the dependency on the
component.

—
Reply to this email directly or view it on GitHub
#22 (comment).

from ngforce.

closing this issue due to inactivity

from ngforce.