Parallelize profile requests #1
Conversation
When a client has requested the `r_emailaddress` scope from LinkedIn, then we do one more request. Instead of firing the requests sequentially we should make both of them at the same time and merge them upon their responses. These requests take aprox. 1 minute when run sequentially, so half a minute when they're run in parallel
|
Looking good! |
|
I couldn't find an issue section in repo so writing here because topic is related. Once I was using https://github.com/jaredhanson/passport-linkedin with older Linkedin API everything was fine. Any idea what's the cause ? |
|
@cigolpl Please make sure that your app has Apart from that, we have also noticed sporadically that for some profiles Linkedin will never return the email even if everything is configured as expected. We've repeatedly tried to troubleshoot that, reached out to Linkedin and reverse engineer any Linkedin profile privacy setting that might be related without success. That is, I'd suggest you also try with two different profiles to see if the problem is resolved. Hope that helps. For the records, |
|
@SokratisVidros it's working now. I've added Thanks for help and that lib. It's huge time saver |
When a client has requested the
r_emailaddressscope from LinkedIn, thenwe do one more request. Instead of firing the requests sequentially we should
make both of them at the same time and merge them upon their responses.
These requests take aprox. 1 second when run sequentially, so half a
second when they're run in parallel