Link


Comments

Post a Comment

Popular posts from this blog

Coupling and (Tight vs Loose)

Image
Coupling in Java In object oriented design, Coupling refers to the degree of direct knowledge that one element has of another. In other words, how often do changes in class A force related changes in class B. There are two types of coupling: Tight coupling :  In general, Tight coupling means the two classes often change together. In other words, if A knows more than it should about the way in which B was implemented, then A and B are tightly coupled. Example :  If you want to change the skin, you would also have to change the design of your body as well because the two are joined together – they are tightly coupled. The best example of tight coupling is RMI(Remote Method Invocation). filter_none brightness_4 // Java program to illustrate // tight coupling concept class Subject {      Topic t = new Topic();      public void startReading()      {     ...
Read more

Asynchronous vs Synchronous Network Call

Synchronous: If an API call is synchronous, it means that code execution will block (or wait) for the API call to return before continuing. This means that until a response is returned by the API, your application will not execute any further, which could be perceived by the user as latency or performance lag in your app. Making an API call synchronously can be beneficial, however, if there if code in your app that will only execute properly once the API response is received. Asynchronous: Asynchronous calls do not block (or wait) for the API call to return from the server. Execution continues on in your program, and when the call returns from the server, a "callback" function is executed. For example, in the following code using the Apigee JavScript SDK, the function called  dogCreateCallback  will be called when the create dog API call returns from the server. Meanwhile, execution will continue: function dogCreateCallback ( err , dog ) {     ...
Read more