Information Technology Broadcasting - اطلاع‌رسانی فناوری اطلاعات
410 subscribers
13.9K photos
41 videos
505 files
489 links
Information Technology, Cloud computing, Digital transformation, IoT, Edge computing, IT governance, Fog computing, IT security, IT regulation, IT trends, Programming، Big data, Monitoring, Databases, Api, Service
Download Telegram
#web concepts

CDN

A CDN (Content Delivery Network) is a group of servers spread out over many locations. These servers store duplicate copies of data so that servers can fulfill data requests based on which servers are closest to the respective end-users. CDNs make for fast service less affected by high traffic.

CDNs are used widely for delivering stylesheets and Javascript files (static assets) of libraries like Bootstrap, jQuery etc. Using CDN for those library files is preferable for a number of reasons:

Serving libraries' static assets over CDN lowers the request burden on our own servers.

Most CDNs have servers all over the globe so CDN's servers may be geographically nearer to your users than your own servers. Geographical distance affects latency proportionally.

CDNs are already configured with proper cache settings. Using a CDN saves further configuration for static assets on your own servers.
#web concept

CORS

CORS (Cross-Origin Resource Sharing) is a system, consisting of transmitting HTTP headers, that determines whether browsers block frontend JavaScript code from accessing responses for cross-origin requests.

The same-origin security policy forbids cross-origin access to resources. But CORS gives web servers the ability to say they want to opt into allowing cross-origin access to their resources.
Forwarded from Hadi
آمریکا ۸۰ تا کانال تلویزیونی خودش رو به صورت لایو و مجانی در اینترنت ارائه کرده روی لینک بزنید تا لیست کانال ها را ببینید و از هر کدوم که خواستید در موبایل استفاده کنید

https://ustvgo.tv/
#web concepts

Short polling vs. Long polling

With the traditional or "short polling" technique, a client sends regular requests to the server and each request attempts to "pull" any available events or data. If there are no events or data available, the server returns an empty response and the client waits for some time before sending another poll request. The polling frequency depends on the latency that the client can tolerate in retrieving updated information from the server. This mechanism has the drawback that the consumed resources (server processing and network) strongly depend on the acceptable latency in the delivery of updates from server to client. If the acceptable latency is low (e.g., on the order of seconds), then the polling frequency can cause an unacceptable burden on the server, the network, or both.

In contrast with such "short polling", "long polling" attempts to minimize both the latency in server-client message delivery and the use of processing/network resources. The server achieves these efficiencies by responding to a request only when a particular event, status, or timeout has occurred. Once the server sends a long poll response, typically the client immediately sends a new long poll request. Effectively, this means that at any given time the server will be holding open a long poll request, to which it replies when new information is available for the client. As a result, the server is able to asynchronously "initiate" communication.