วีดีโอ

Baba Nam Kevalam

Very well explained. Thank you. You have a clear cut knowledge on the topics, that reflects in your way of teaching. Please continue to post videos and support.

Great series! Thank you

Great explanation! looking forward to more contents from you..

Superb tutorial Viraj.

What an ugly design!

Stolen from python

Omg

Weird

Unbelievable

Why?

Very well explained - one of the best videos on TH-cam for ease of understanding - subscribed!

I know very little about method references earlier, had many doubts. I have clear understanding, after watching this lecture. Thanks a lot Sir.

Nice overview. Some code samples would have been nice, though

Really really great explanation.

Not enough likes considering the quality of the content here

Please cover some examples of streams with optional

for the case where we have many tasks submitted, do we have to manually compare are the future as (future == taskXfuture) ? id there any inbuilt way to deal with such requirements

Excellent! Basically every application has to do its own authorization. What you are calling as 'Enterprise Authorization' is where LMS is authorizing the user to do something in the LMS app itself. Obviously, if the user wants to post his learning cert to LinkedIN - that is now an action he is talking in the LinkedIN app - and therefore LinkedIn has to do the authorization for that posting action. This is what you are calling as oAuth Authorization. oAuth is the protocol that allows LMS to take the action in ON BEHALF of the user, in the LinkedIN app. AUTHENTICATION however, does not need to be done by the application itself (and is actually better if it is not) - and can be instead centralized instead in a IDENTITY MANAGEMENT application . Authentication can therefore be done either through a centralized Enterprise Identity Management solution (like Okta) , or using social identities (like Google ID) which leverage the OpenID Connect protocol

Another excellent video! In the other video, you had described oAuth as more of the authorization protocol (eg to post to LinkedIn and FB) , and not so much as a authentication protocol (you mentioned OIDC as more of an authentication protocol). So I am curious why in this video , you are referring to oAuth as a 'Delegated AUTHENTICATION' protocol?

Excellent video ! Couple of Suggestions - (1) In the middle there , you started talking about Google/Apple authentication, and then went back and drew the picture for linkedin and FB . Suggest fixing that , because it breaks the flow (2) Towards the end, when you were talking about enterprise apps, and you had said the apps may be interested in access tokens as well - I was unclear on where the LMS is getting the access tokens from, when talking to Google / Apple

Quality content

Thank you for explaining. For those coming from Kotlin coroutines, it sounds like Futures are analogous to Deferred<V> (or Job).

Mann,what a lecture cleared all the doubts. Initially I had so many doubts but gradually you cleared all of them

GREATTT VIDEO, VIRAJ CLEARED MANY DOUBTS

Hi vijay, doubt from india. I have few doubts Task-2 will execute in a separate thread??? 2) .thenCombine().thenApply() in this method chaining, these methods execute concurrently/parallely or one after the other??

6:47 output is of hex format, not base64. Thank you for the quick hands-on! 😊

Great series 👏

Very nice explanation.Thanks for this series

With your explanation, it seems login with Google or Facebook option on websites is using openId connect. Am I correct?

reactive programming is abstration gone wrong, just like FP

Wonderful explanation

Very nice and clear explanation !!

very nicely explained Viraj. Good job

Simply superb. Stand and deliver style

final class has the function of making the generated class uninheritable

Thanks for clear explanation.. Kudos 🎉

13:19 I am not going to use anymore

10:55 Automatic switching is cool

Thanks for this video. By the way your Virtual Threads course is best out there.

Thanks! Nice explanation for use cases of OAuth and OpenID connect.

Hi Viraj, one question. when we use thenApplyAsync and supplyAsync methods in pipeline, these will be exectued by different threads, do not know, when supplyAsync will complete the execution of the task then how thenApplyAsync() will get know when the previous task is completed.

Very nice explanation Viraj. Thank you.

Very good explanation...

Perfect

Wow great explanation. Please create more videos covering end to end

Cool , thanks

This just adds unnecessary complexity making the code unreadable and un-maintainable. Why not just write for loops and keep it simple? Streams do not provide any performance advantage over loops.

Yes, please. Do create some extra videos with examples. Better still add in one of your Udemy courses, or create a new one, please.

Please create a udemy course on Core Java (deep dive).