EventSource<\/a> API’si ile \u00e7al\u0131\u015f\u0131r\u0131z. Bu API, sunucu taraf\u0131ndan g\u00f6nderilen olaylar\u0131 dinlemek ve i\u015flemek i\u00e7in basit bir aray\u00fcz sa\u011flar. \u00d6ncelikle, bir HTML dosyas\u0131na ihtiyac\u0131m\u0131z olacak:\n <\/p>\n\n\n\n\n \n \n SSE \u00d6rne\u011fi: Canl\u0131 Saat<\/title>\n <style>\n body { font-family: sans-serif; display: flex; justify-content: center; align-items: center; min-height: 100vh; background-color: #f0f0f0; margin: 0; }\n .container { background: white; padding: 40px; border-radius: 8px; box-shadow: 0 4px 8px rgba(0,0,0,0.1); text-align: center; }\n #live-time { font-size: 3em; color: #333; margin-top: 20px; }\n .status { margin-top: 15px; font-size: 0.9em; color: #666; }\n .status.connected { color: green; }\n .status.disconnected { color: red; }\n @media (max-width: 768px) {\n .container { padding: 20px; }\n #live-time { font-size: 2em; }\n }\n <\/style>\n<\/head>\n<body>\n <div class=\"container\">\n <h1>Canl\u0131 Sunucu Saati<\/h1>\n <div id=\"live-time\">Y\u00fckleniyor...<\/div>\n <div class=\"status\" id=\"connection-status\">Ba\u011flan\u0131l\u0131yor...<\/div>\n <\/div>\n\n <script>\n const liveTimeElement = document.getElementById('live-time');\n const statusElement = document.getElementById('connection-status');\n let eventSource;\n\n function connectSSE() {\n if (eventSource) {\n eventSource.close(); \/\/ \u00d6nceki ba\u011flant\u0131y\u0131 kapat\n }\n statusElement.textContent = 'Ba\u011flan\u0131l\u0131yor...';\n statusElement.className = 'status';\n\n \/\/ EventSource nesnesi olu\u015fturma. Parametre, SSE ak\u0131\u015f\u0131n\u0131 sa\u011flayan sunucu URL'sidir.\n eventSource = new EventSource('\/stream-time');\n\n \/\/ Sunucudan gelen her mesajda tetiklenir\n eventSource.onmessage = function(event) {\n \/\/ event.data, sunucudan gelen veriyi i\u00e7erir\n liveTimeElement.textContent = event.data;\n };\n\n \/\/ Ba\u011flant\u0131 a\u00e7\u0131ld\u0131\u011f\u0131nda tetiklenir\n eventSource.onopen = function() {\n console.log('SSE Ba\u011flant\u0131s\u0131 A\u00e7\u0131ld\u0131.');\n statusElement.textContent = 'Ba\u011fl\u0131';\n statusElement.className = 'status connected';\n };\n\n \/\/ Ba\u011flant\u0131 hatas\u0131 olu\u015ftu\u011funda tetiklenir\n eventSource.onerror = function(error) {\n console.error('SSE Hatas\u0131:', error);\n statusElement.textContent = 'Ba\u011flant\u0131 Hatas\u0131! Yeniden ba\u011flan\u0131l\u0131yor...';\n statusElement.className = 'status disconnected';\n \/\/ EventSource, varsay\u0131lan olarak ba\u011flant\u0131 kesintilerinde otomatik olarak yeniden ba\u011flanmay\u0131 dener.\n \/\/ Manuel bir m\u00fcdahaleye genellikle gerek yoktur, ancak karma\u015f\u0131k durumlar i\u00e7in burada ekstra mant\u0131k eklenebilir.\n };\n }\n\n document.addEventListener('DOMContentLoaded', connectSSE);\n <\/script>\n<\/body>\n<\/html>\n <\/pre>\n<p><\/code><\/p>\n<p>\n Yukar\u0131daki kodda, <code>new EventSource('\/stream-time')<\/code> ile sunucumuzdaki <code>\/stream-time<\/code> endpoint'ine bir SSE ba\u011flant\u0131s\u0131 kuruyoruz. <code>onmessage<\/code> olay\u0131, sunucudan gelen her yeni veri par\u00e7as\u0131n\u0131 yakalar ve <code>live-time<\/code> etiketini g\u00fcnceller. <code>onopen<\/code> ve <code>onerror<\/code> olaylar\u0131 ise ba\u011flant\u0131 durumunu izlememizi sa\u011flar. <code>EventSource<\/code> nesnesinin en g\u00fczel \u00f6zelliklerinden biri, ba\u011flant\u0131 kesintilerinde (\u00f6rne\u011fin a\u011f sorunlar\u0131 nedeniyle) otomatik olarak yeniden ba\u011flanmaya \u00e7al\u0131\u015fmas\u0131d\u0131r. Bu, uygulaman\u0131z\u0131n sa\u011flaml\u0131\u011f\u0131n\u0131 art\u0131r\u0131r.\n <\/p>\n<aside class=\"tip\">\n Uzman \u0130pucu: EventSource'un otomatik yeniden ba\u011flanma \u00f6zelli\u011fi, \u00f6zellikle mobil cihazlarda veya de\u011fi\u015fken a\u011f ko\u015fullar\u0131nda kullan\u0131c\u0131 deneyimini \u00f6nemli \u00f6l\u00e7\u00fcde iyile\u015ftirir. Varsay\u0131lan olarak, ba\u011flant\u0131 kesildi\u011finde belirli bir s\u00fcre sonra tekrar ba\u011flanmay\u0131 dener. Bu davran\u0131\u015f\u0131 sunucu taraf\u0131ndan <code>retry:<\/code> alan\u0131 ile \u00f6zelle\u015ftirebilirsiniz.<br \/>\n <\/aside>\n<h3>Sunucu Taraf\u0131: Bir SSE Ak\u0131\u015f\u0131 Nas\u0131l Olu\u015fturulur?<\/h3>\n<p>\n Sunucu taraf\u0131nda, herhangi bir programlama dilini (Node.js, Python, PHP, Ruby vb.) kullanarak bir HTTP endpoint'i olu\u015fturman\u0131z ve belirli HTTP ba\u015fl\u0131klar\u0131n\u0131 ayarlayarak <code>text\/event-stream<\/code> format\u0131nda veri g\u00f6ndermeniz gerekir. A\u015fa\u011f\u0131da, Node.js ve Express kullanarak basit bir \u00f6rnek g\u00f6sterilmi\u015ftir. Di\u011fer dillerde de benzer mant\u0131kla hareket edilir.\n <\/p>\n<pre><code>\n\/\/ Node.js ve Express kullanarak basit bir SSE sunucusu\nconst express = require('express');\nconst app = express();\nconst PORT = 3000;\n\n\/\/ \u0130stemciye ba\u011flanacak statik HTML dosyam\u0131z\u0131 sunal\u0131m\napp.use(express.static('public')); \/\/ 'public' klas\u00f6r\u00fcnde index.html dosyan\u0131z oldu\u011funu varsayal\u0131m\n\napp.get('\/stream-time', (req, res) => {\n \/\/ SSE ba\u011flant\u0131s\u0131 i\u00e7in gerekli ba\u015fl\u0131klar\u0131 ayarla\n res.setHeader('Content-Type', 'text\/event-stream');\n res.setHeader('Cache-Control', 'no-cache');\n res.setHeader('Connection', 'keep-alive'); \/\/ Ba\u011flant\u0131y\u0131 a\u00e7\u0131k tut\n\n \/\/ Belirli aral\u0131klarla istemciye veri g\u00f6nder\n const intervalId = setInterval(() => {\n const currentTime = new Date().toLocaleTimeString();\n \/\/ SSE format\u0131: 'data: [veri]\\n\\n'\n res.write(<code>data: ${currentTime}\\n\\n<\/code>);\n }, 1000); \/\/ Her 1 saniyede bir g\u00f6nder\n\n \/\/ \u0130stemci ba\u011flant\u0131y\u0131 kapatt\u0131\u011f\u0131nda, interval'\u0131 temizle\n req.on('close', () => {\n clearInterval(intervalId);\n console.log('\u0130stemci ba\u011flant\u0131s\u0131 kapat\u0131ld\u0131.');\n });\n\n console.log('Yeni SSE istemcisi ba\u011fland\u0131.');\n});\n\napp.listen(PORT, () => {\n console.log(<code>SSE Sunucusu http:\/\/localhost:${PORT} adresinde \u00e7al\u0131\u015f\u0131yor.<\/code>);\n});\n <\/pre>\n<p><\/code><\/p>\n<p>\n Bu Node.js \u00f6rne\u011finde:\n <\/p>\n<ul>\n<li><code>res.setHeader('Content-Type', 'text\/event-stream');<\/code>: Bu ba\u015fl\u0131k, taray\u0131c\u0131ya gelen verinin bir SSE ak\u0131\u015f\u0131 oldu\u011funu bildirir. Bu ba\u015fl\u0131k <strong>kesinlikle<\/strong> gereklidir.<\/li>\n<li><code>res.setHeader('Cache-Control', 'no-cache');<\/code> ve <code>res.setHeader('Connection', 'keep-alive');<\/code>: Bu ba\u015fl\u0131klar, taray\u0131c\u0131n\u0131n yan\u0131t\u0131 \u00f6nbelle\u011fe almamas\u0131n\u0131 ve ba\u011flant\u0131y\u0131 a\u00e7\u0131k tutmas\u0131n\u0131 sa\u011flar.<\/li>\n<li><code>res.write(<code>data: ${currentTime}\\n\\n<\/code>);<\/code>: Sunucuya g\u00f6nderilecek veriyi bu formatta yaz\u0131yoruz. Her veri par\u00e7as\u0131 <code>data:<\/code> ile ba\u015flamal\u0131 ve iki sat\u0131r sonu (<code>\\n\\n<\/code>) ile bitmelidir. Bu iki sat\u0131r sonu, taray\u0131c\u0131ya bir olay\u0131n sona erdi\u011fini ve ayr\u0131\u015ft\u0131r\u0131labilece\u011fini bildirir.<\/li>\n<li><code>setInterval<\/code>: Bu fonksiyon, her saniye yeni bir zaman bilgisi olu\u015fturup istemciye g\u00f6nderir.<\/li>\n<li><code>req.on('close', ...)<\/code>: \u0130stemci taray\u0131c\u0131y\u0131 kapatt\u0131\u011f\u0131nda veya ba\u011flant\u0131 koptu\u011funda, sunucunun gereksiz kaynaklar\u0131 (<code>intervalId<\/code> gibi) serbest b\u0131rakmas\u0131 \u00f6nemlidir.<\/li>\n<\/ul>\n<p>\n Bu ad\u0131mlarla, basit ama i\u015flevsel bir Server-Sent Events uygulamas\u0131 olu\u015fturmu\u015f olursunuz. \u0130stemci taraf\u0131ndaki HTML dosyas\u0131n\u0131 bir <code>public<\/code> klas\u00f6r\u00fcne yerle\u015ftirip Node.js sunucusunu \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda, taray\u0131c\u0131n\u0131zda canl\u0131 olarak g\u00fcncellenen zaman\u0131 g\u00f6receksiniz. Bu temel yap\u0131, ger\u00e7ek d\u00fcnya senaryolar\u0131nda daha karma\u015f\u0131k olaylar\u0131 ve verileri g\u00f6ndermek i\u00e7in kolayca geni\u015fletilebilir. \u00d6rne\u011fin, <code>event: customEventName\\n<\/code> gibi bir alan ekleyerek farkl\u0131 olay t\u00fcrlerini tetikleyebilir ve istemci taraf\u0131nda <code>eventSource.addEventListener('customEventName', function(event) { ... });<\/code> ile bu olaylar\u0131 dinleyebilirsiniz.\n <\/p>\n<h2>Ger\u00e7ek D\u00fcnya Senaryolar\u0131: Server-Sent Events Nerelerde Hayat Kurtar\u0131r?<\/h2>\n<p>\n Server-Sent Events'in (SSE) g\u00fcc\u00fc ve basitli\u011fi, onu bir\u00e7ok ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131 ihtiyac\u0131 i\u00e7in ideal bir \u00e7\u00f6z\u00fcm haline getirir. WebSockets'in \u00e7ift y\u00f6nl\u00fc ileti\u015fim karma\u015f\u0131kl\u0131\u011f\u0131na ihtiya\u00e7 duymayan, sunucudan istemciye tek y\u00f6nl\u00fc veri ak\u0131\u015f\u0131n\u0131n yeterli oldu\u011fu senaryolarda SSE parlar. \u0130\u015fte SSE'nin ger\u00e7ek d\u00fcnyada ba\u015far\u0131yla kullan\u0131ld\u0131\u011f\u0131 baz\u0131 yayg\u0131n senaryolar ve vaka analizleri:\n <\/p>\n<h3>Canl\u0131 Haber Ak\u0131\u015flar\u0131 ve Anl\u0131k Bildirimler: Kullan\u0131c\u0131lar\u0131 G\u00fcncel Tutmak<\/h3>\n<p>\n Haber siteleri, bloglar veya sosyal medya platformlar\u0131 gibi i\u00e7erik odakl\u0131 uygulamalarda, kullan\u0131c\u0131lara yeni i\u00e7eriklerin veya \u00f6nemli duyurular\u0131n an\u0131nda ula\u015ft\u0131r\u0131lmas\u0131 b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r. Geleneksel olarak, kullan\u0131c\u0131lar\u0131n yeni haberleri g\u00f6rmek i\u00e7in sayfay\u0131 manuel olarak yenilemesi veya sitenin belirli aral\u0131klarla sunucuya sorgu g\u00f6ndermesi (polling) gerekirdi. Polling, gereksiz a\u011f trafi\u011fi ve sunucu y\u00fck\u00fc yarat\u0131rken, manuel yenileme kullan\u0131c\u0131 deneyimini k\u00f6t\u00fcle\u015ftirir.<br \/>\n SSE, bu soruna \u015f\u0131k bir \u00e7\u00f6z\u00fcm sunar. Bir haber sitesi, yeni bir makale yay\u0131nland\u0131\u011f\u0131nda veya \u00f6nemli bir man\u015fet g\u00fcncellendi\u011finde, bu bilgiyi t\u00fcm ba\u011fl\u0131 istemcilere bir SSE ak\u0131\u015f\u0131 \u00fczerinden g\u00f6nderebilir. \u00d6rne\u011fin, sunucu yeni bir haber objesi olu\u015fturdu\u011funda, bunu <code>data: { \"id\": \"123\", \"title\": \"Yeni Geli\u015fme!\", \"url\": \"\/yeni-gelisme\" }\\n\\n<\/code> format\u0131nda yay\u0131nlayabilir. \u0130stemci taraf\u0131nda \u00e7al\u0131\u015fan JavaScript kodu, bu olay\u0131 yakalayarak ekran\u0131n \u00fcst k\u0131sm\u0131nda bir bildirim g\u00f6sterebilir veya haber ak\u0131\u015f\u0131n\u0131 an\u0131nda g\u00fcncelleyebilir.<br \/>\n <strong>Vaka Analizi:<\/strong> Bir sosyal medya platformu, kullan\u0131c\u0131lar\u0131n arkada\u015fl\u0131k istekleri, be\u011feniler veya yorumlar gibi anl\u0131k bildirimleri i\u00e7in SSE kullanabilir. Sunucu, bir kullan\u0131c\u0131ya yeni bir bildirim geldi\u011finde, ilgili bildirim verilerini SSE ak\u0131\u015f\u0131 \u00fczerinden istemciye g\u00f6nderir ve istemci an\u0131nda bir pop-up veya bildirim simgesinde artan bir say\u0131 g\u00f6sterir. Bu, kullan\u0131c\u0131lar\u0131n uygulamay\u0131 daha aktif kullanmas\u0131n\u0131 te\u015fvik eder ve s\u00fcrekli g\u00fcncellenmi\u015f hissi verir. Tek y\u00f6nl\u00fc bir ak\u0131\u015f oldu\u011fu i\u00e7in, kullan\u0131c\u0131n\u0131n bu bildirimlere yan\u0131t vermesi (\u00f6rne\u011fin bir iste\u011fi kabul etmesi) yine standart AJAX istekleri ile yap\u0131labilir.\n <\/p>\n<h3>Finans Uygulamalar\u0131 ve Hisse Senedi Takibi: Verileri An\u0131nda Yay\u0131nlamak<\/h3>\n<p>\n Finans piyasalar\u0131, saniyeler i\u00e7inde de\u011fi\u015fen veri ak\u0131\u015f\u0131yla karakterizedir. Hisse senedi fiyatlar\u0131, d\u00f6viz kurlar\u0131, emtia fiyatlar\u0131 ve borsa endeksleri gibi verilerin ger\u00e7ek zamanl\u0131 olarak izlenmesi, yat\u0131r\u0131mc\u0131lar ve analistler i\u00e7in hayati \u00f6neme sahiptir. Burada gecikme kabul edilemez olabilir. SSE, bu t\u00fcr uygulamalar i\u00e7in do\u011fal bir uyum sa\u011flar.<br \/>\n Bir finans uygulamas\u0131, belirli hisse senedi veya kripto para birimi fiyatlar\u0131n\u0131 bir SSE ak\u0131\u015f\u0131 \u00fczerinden s\u00fcrekli olarak yay\u0131nlayabilir. Sunucu, bir veri sa\u011flay\u0131c\u0131dan gelen g\u00fcncel fiyat bilgilerini al\u0131r almaz, bunu t\u00fcm ba\u011fl\u0131 izleme panellerine veya uygulamalara an\u0131nda iletir. Her bir veri paketi, \u00f6rne\u011fin <code>data: { \"symbol\": \"XYZ\", \"price\": 150.75, \"change\": \"+0.50\" }\\n\\n<\/code> \u015feklinde g\u00f6nderilebilir. \u0130stemci taraf\u0131nda, bu veriler bir tabloyu veya grafik widget'\u0131n\u0131 saniyeler i\u00e7inde g\u00fcncelleyebilir.<br \/>\n <strong>Vaka Analizi:<\/strong> Bir borsa takip platformu, kullan\u0131c\u0131lar\u0131n favori hisse senetleri listesini SSE ile g\u00fcncel tutar. Kullan\u0131c\u0131 bir hisse senedi ekledi\u011finde veya \u00e7\u0131kard\u0131\u011f\u0131nda, sunucuya bir AJAX iste\u011fi g\u00f6nderilir ve sunucu, sadece o hisse senedinin verilerini i\u00e7eren bir SSE ak\u0131\u015f\u0131 ba\u015flat\u0131r veya mevcut ak\u0131\u015f\u0131 g\u00fcnceller. Bu sayede, binlerce kullan\u0131c\u0131n\u0131n binlerce farkl\u0131 hisse senedini e\u015f zamanl\u0131 olarak, ancak sadece ihtiya\u00e7 duyduklar\u0131 verilerle izlemesi sa\u011flan\u0131r. Kullan\u0131c\u0131lar\u0131n hisse senedi al\u0131m\/sat\u0131m emirleri gibi etkile\u015fimli i\u015flemler yine AJAX veya WebSockets ile yap\u0131l\u0131rken, fiyat g\u00fcncellemeleri i\u00e7in SSE kullan\u0131l\u0131r ve bu durum sistemi daha hafif ve verimli k\u0131lar.\n <\/p>\n<h3>Y\u00f6netici Panelleri ve Analitik G\u00f6sterge Tablolar\u0131: Ger\u00e7ek Zamanl\u0131 Metrikler<\/h3>\n<p>\n Web sitelerinin veya uygulamalar\u0131n performans\u0131n\u0131, kullan\u0131c\u0131 etkinliklerini veya sunucu sa\u011fl\u0131\u011f\u0131n\u0131 izleyen y\u00f6netici panelleri ve analitik g\u00f6sterge tablolar\u0131, ger\u00e7ek zamanl\u0131 metrikleri an\u0131nda sunma ihtiyac\u0131 duyar. Ziyaret\u00e7i say\u0131lar\u0131, sunucu CPU kullan\u0131m\u0131, hata loglar\u0131, sipari\u015f ak\u0131\u015flar\u0131 gibi verilerin s\u00fcrekli g\u00fcncellenmesi, y\u00f6neticilerin h\u0131zl\u0131 kararlar almas\u0131n\u0131 sa\u011flar.<br \/>\n SSE, sunucunun sistemden veya veritaban\u0131ndan toplad\u0131\u011f\u0131 g\u00fcncel metrikleri periyodik olarak veya anl\u0131k olarak g\u00f6sterge tablolar\u0131na aktarmas\u0131na olanak tan\u0131r. \u00d6rne\u011fin, bir sunucu izleme arac\u0131, her 5 saniyede bir CPU kullan\u0131m\u0131n\u0131 ve bellek t\u00fcketimini \u00e7ekip <code>data: { \"cpu\": \"35%\", \"mem\": \"60%\" }\\n\\n<\/code> \u015feklinde g\u00f6nderebilir. \u0130stemci taraf\u0131nda, bu veriler dinamik grafikler veya saya\u00e7lar \u00fczerinde g\u00f6rselle\u015ftirilebilir.<br \/>\n <strong>Vaka Analizi:<\/strong> Bir e-ticaret sitesinin y\u00f6netici paneli, yeni sipari\u015flerin anl\u0131k olarak g\u00f6r\u00fcnt\u00fclenmesi, stok seviyelerinin takip edilmesi ve m\u00fc\u015fteri hizmetleri taleplerinin izlenmesi i\u00e7in SSE'yi kullanabilir. Her yeni sipari\u015f geldi\u011finde, sistem otomatik olarak SSE ak\u0131\u015f\u0131na bir olay g\u00f6nderir ve bu olay, y\u00f6neticinin ekran\u0131ndaki \"Yeni Sipari\u015fler\" listesini veya bir sipari\u015f sayac\u0131n\u0131 an\u0131nda g\u00fcnceller. Bu, y\u00f6neticilerin sipari\u015fleri daha h\u0131zl\u0131 i\u015flemesini ve m\u00fc\u015fteri memnuniyetini art\u0131rmas\u0131n\u0131 sa\u011flar. Kullan\u0131c\u0131n\u0131n bir sipari\u015fi \"i\u015flendi\" olarak i\u015faretlemesi gibi etkile\u015fimli eylemler ise yine geleneksel HTTP istekleriyle ger\u00e7ekle\u015ftirilir. Bu senaryolarda SSE'nin tek y\u00f6nl\u00fc do\u011fas\u0131, ihtiya\u00e7 duyulan ger\u00e7ek zamanl\u0131l\u0131\u011f\u0131 sa\u011flarken, sistemin mimarisini gereksiz yere karma\u015f\u0131kla\u015ft\u0131rmaz.\n <\/p>\n<h2>\u0130leri D\u00fczey Konular: Performans, \u00d6l\u00e7eklenebilirlik ve Hata Y\u00f6netimi \u0130\u00e7in \u0130pu\u00e7lar\u0131<\/h2>\n<p>\n Server-Sent Events (SSE) temel olarak basit bir teknoloji olsa da, ger\u00e7ek d\u00fcnya uygulamalar\u0131nda performans, \u00f6l\u00e7eklenebilirlik ve hata y\u00f6netimi konular\u0131n\u0131 g\u00f6z \u00f6n\u00fcnde bulundurmak, sa\u011flam ve verimli sistemler olu\u015fturmak i\u00e7in kritik \u00f6neme sahiptir. Bu b\u00f6l\u00fcmde, SSE uygulamalar\u0131n\u0131z\u0131 daha g\u00fc\u00e7l\u00fc hale getirecek baz\u0131 ileri d\u00fczey konulara de\u011finece\u011fiz.\n <\/p>\n<h3>Yeniden Ba\u011flanma ve Durum Y\u00f6netimi: Ba\u011flant\u0131 Kesintileri Nas\u0131l Ele Al\u0131n\u0131r?<\/h3>\n<p>\n SSE'nin en b\u00fcy\u00fck avantajlar\u0131ndan biri, istemci taraf\u0131ndaki <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/EventSource\">EventSource<\/a> API'sinin yerle\u015fik otomatik yeniden ba\u011flanma \u00f6zelli\u011fidir. A\u011f kesintileri, sunucu yeniden ba\u015flatmalar\u0131 veya ge\u00e7ici ba\u011flant\u0131 sorunlar\u0131 durumunda, <code>EventSource<\/code> nesnesi otomatik olarak ba\u011flant\u0131y\u0131 yeniden kurmaya \u00e7al\u0131\u015f\u0131r. Varsay\u0131lan olarak, bu yeniden ba\u011flanma giri\u015fimi 3 saniye sonra yap\u0131l\u0131r, ancak sunucu bu s\u00fcreyi <code>retry: [milisaniye]\\n<\/code> alan\u0131 ile \u00f6zelle\u015ftirebilir. \u00d6rne\u011fin, <code>retry: 10000\\n\\n<\/code> istemciye 10 saniye sonra yeniden ba\u011flanmay\u0131 denemesini s\u00f6yler.<br \/>\n Bu otomatik yeniden ba\u011flanma \u00f6zelli\u011fi, \u00f6zellikle mobil a\u011flarda veya g\u00fcvenilmez internet ba\u011flant\u0131lar\u0131nda kullan\u0131c\u0131 deneyimini \u00f6nemli \u00f6l\u00e7\u00fcde iyile\u015ftirir. Ancak, ba\u011flant\u0131 yeniden kuruldu\u011funda, istemcinin hangi verileri ka\u00e7\u0131rd\u0131\u011f\u0131n\u0131 bilmesi ve eksik verileri talep etmesi gerekebilir. \u0130\u015fte burada <code>Last-Event-ID<\/code> ba\u015fl\u0131\u011f\u0131 devreye girer. Sunucu, her olayla birlikte bir <code>id: [olay_kimli\u011fi]\\n<\/code> alan\u0131 g\u00f6nderebilir. <code>EventSource<\/code> istemcisi, yeniden ba\u011flanma iste\u011fi yaparken, en son ald\u0131\u011f\u0131 olay\u0131n kimli\u011fini <code>Last-Event-ID<\/code> HTTP ba\u015fl\u0131\u011f\u0131 ile sunucuya g\u00f6nderir. Sunucu bu ba\u015fl\u0131\u011f\u0131 okuyarak, istemcinin nerede kald\u0131\u011f\u0131n\u0131 anlayabilir ve sadece ka\u00e7\u0131rd\u0131\u011f\u0131 olaylar\u0131 veya yeni olaylar\u0131 g\u00f6ndermeye ba\u015flayabilir. Bu, \"olay kaynaklama\" (event sourcing) yakla\u015f\u0131mlar\u0131yla veya bir mesaj kuyru\u011fu sistemiyle entegre edilerek g\u00fc\u00e7l\u00fc bir durum senkronizasyonu sa\u011flanabilir.\n <\/p>\n<h3>Performans ve \u00d6l\u00e7eklenebilirlik Optimizasyonlar\u0131: Y\u00fcksek Y\u00fckl\u00fc Sistemler \u0130\u00e7in Ne Yapmal\u0131?<\/h3>\n<p>\n SSE, WebSockets'e k\u0131yasla daha hafif olsa da, binlerce veya on binlerce e\u015fzamanl\u0131 ba\u011flant\u0131y\u0131 y\u00f6netmek yine de sunucu kaynaklar\u0131 \u00fczerinde \u00f6nemli bir y\u00fck olu\u015fturabilir. Her bir a\u00e7\u0131k SSE ba\u011flant\u0131s\u0131, sunucuda bir dosya tan\u0131t\u0131c\u0131s\u0131 (file descriptor) ve bir miktar bellek t\u00fcketir.\n <\/p>\n<ul>\n<li><strong>HTTP\/2 Kullan\u0131m\u0131:<\/strong> HTTP\/2 protokol\u00fc, ayn\u0131 TCP ba\u011flant\u0131s\u0131 \u00fczerinden birden fazla ak\u0131\u015fa izin verdi\u011fi i\u00e7in SSE'nin performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131rabilir. Bu, her SSE ak\u0131\u015f\u0131 i\u00e7in ayr\u0131 bir TCP ba\u011flant\u0131s\u0131 a\u00e7ma ihtiyac\u0131n\u0131 ortadan kald\u0131r\u0131r.<\/li>\n<li><strong>Y\u00fck Dengeleyiciler ve Proxy'ler:<\/strong> SSE ak\u0131\u015flar\u0131, genellikle mevcut y\u00fck dengeleyiciler ve ters proxy'lerle (nginx, HaProxy vb.) sorunsuz \u00e7al\u0131\u015f\u0131r. Ancak, baz\u0131 proxy'ler varsay\u0131lan olarak HTTP yan\u0131tlar\u0131n\u0131 arabelle\u011fe alabilir. Bu, verilerin istemciye an\u0131nda ula\u015fmas\u0131n\u0131 engelleyebilir. Bu durumu \u00f6nlemek i\u00e7in, proxy yap\u0131land\u0131rman\u0131zda SSE ak\u0131\u015flar\u0131 i\u00e7in arabelle\u011fe almay\u0131 (buffering) kapatman\u0131z \u00f6nemlidir. \u00d6rne\u011fin, Nginx i\u00e7in <code>proxy_buffering off;<\/code> ayar\u0131 kullan\u0131labilir.<\/li>\n<li><strong>Sunucu Taraf\u0131 Optimizasyonlar:<\/strong> Sunucu taraf\u0131nda, olaylar\u0131 verimli bir \u015fekilde y\u00f6netmek i\u00e7in optimize edilmi\u015f \u00e7\u00f6z\u00fcmler kullanmak \u00f6nemlidir. \u00d6rne\u011fin, bir mesaj kuyru\u011fu sistemi (RabbitMQ, Kafka) kullanarak olaylar\u0131 yay\u0131nlayabilir ve SSE sunucusu bu kuyruklardan olaylar\u0131 al\u0131p istemcilere iletebilir. Bu, olay \u00fcretimini ve da\u011f\u0131t\u0131m\u0131n\u0131 birbirinden ay\u0131rarak \u00f6l\u00e7eklenebilirli\u011fi art\u0131r\u0131r. Olaylar\u0131 do\u011frudan veritaban\u0131ndan \u00e7ekmek yerine, \u00f6nbellek (Redis) kullanarak performans\u0131 art\u0131rabilirsiniz.<\/li>\n<li><strong>Ba\u011flant\u0131 Ba\u015f\u0131na Veri Yo\u011funlu\u011fu:<\/strong> Her istemciye s\u00fcrekli ve yo\u011fun veri g\u00f6ndermekten ka\u00e7\u0131n\u0131n. Yaln\u0131zca ger\u00e7ekten gerekli olan verileri g\u00f6nderin ve veri paketlerini m\u00fcmk\u00fcn oldu\u011funca k\u00fc\u00e7\u00fck tutun. \u0130stemci taraf\u0131nda, al\u0131nan verilerin i\u015flenmesi de performans a\u00e7\u0131s\u0131ndan \u00f6nemlidir; gereksiz DOM manip\u00fclasyonlar\u0131ndan ka\u00e7\u0131n\u0131n.<\/li>\n<\/ul>\n<h3>G\u00fcvenlik Hususlar\u0131: Verileri G\u00fcvende Tutmak<\/h3>\n<p>\n SSE, HTTP\/1.1 \u00fczerine kuruldu\u011fu i\u00e7in, mevcut HTTP g\u00fcvenlik mekanizmalar\u0131n\u0131n \u00e7o\u011fundan yararlan\u0131r.\n <\/p>\n<ul>\n<li><strong>HTTPS Kullan\u0131m\u0131:<\/strong> T\u00fcm ger\u00e7ek zamanl\u0131 uygulamalarda oldu\u011fu gibi, SSE ba\u011flant\u0131lar\u0131 i\u00e7in de HTTPS (<code>https:\/\/<\/code> veya <code>EventSource<\/code> i\u00e7in <code>wss:\/\/<\/code> gibi bir \u015fey yok, SSE zaten HTTPS \u00fczerinden \u00e7al\u0131\u015f\u0131r) kullanmak zorunludur. Bu, verilerin \u015fifreli olarak iletilmesini ve man-in-the-middle sald\u0131r\u0131lar\u0131ndan korunmas\u0131n\u0131 sa\u011flar.<\/li>\n<li><strong>Kimlik Do\u011frulama ve Yetkilendirme:<\/strong> SSE endpoint'leri de di\u011fer HTTP endpoint'leri gibi korunmal\u0131d\u0131r. JWT (JSON Web Tokens), oturum \u00e7erezleri veya API anahtarlar\u0131 gibi y\u00f6ntemlerle kullan\u0131c\u0131 kimlik do\u011frulamas\u0131 ve yetkilendirmesi yap\u0131lmal\u0131d\u0131r. Sunucu, sadece yetkili istemcilere SSE ak\u0131\u015f\u0131 sunmal\u0131 ve yaln\u0131zca ilgili verilere eri\u015fim izni vermelidir.<\/li>\n<li><strong>Cross-Origin Kaynak Payla\u015f\u0131m\u0131 (CORS):<\/strong> E\u011fer SSE sunucunuz ve istemciniz farkl\u0131 domainlerde bulunuyorsa, CORS ba\u015fl\u0131klar\u0131n\u0131 do\u011fru yap\u0131land\u0131rman\u0131z gerekir (<code>Access-Control-Allow-Origin<\/code>). Aksi takdirde, taray\u0131c\u0131 g\u00fcvenlik politikalar\u0131 nedeniyle ba\u011flant\u0131 kurulamaz.<\/li>\n<\/ul>\n<h3>Mobil Uyumluluk: Farkl\u0131 Cihazlarda Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/h3>\n<p>\n SSE, modern taray\u0131c\u0131lar\u0131n b\u00fcy\u00fck \u00e7o\u011funlu\u011fu taraf\u0131ndan desteklenmektedir, bu da mobil cihazlarda da sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131 anlam\u0131na gelir. iOS Safari, Android Chrome ve di\u011fer mobil taray\u0131c\u0131lar <code>EventSource<\/code> API'sini destekler. Ancak, mobil a\u011flar\u0131n de\u011fi\u015fken do\u011fas\u0131 (ba\u011flant\u0131 kesintileri, bant geni\u015fli\u011fi dalgalanmalar\u0131) nedeniyle yukar\u0131da bahsedilen otomatik yeniden ba\u011flanma ve <code>Last-Event-ID<\/code> kullan\u0131m\u0131 daha da \u00f6nem kazan\u0131r. Mobil uyumlu bir kullan\u0131c\u0131 aray\u00fcz\u00fc sa\u011flamak i\u00e7in CSS media query'lerini kullanmak genel bir iyi pratiktir:\n <\/p>\n<pre><code>\n<style>\n \/* Varsay\u0131lan stil *\/\n .content-wrapper {\n padding: 20px;\n margin: 10px;\n border: 1px solid #ccc;\n background-color: #fff;\n }\n\n \/* 768px geni\u015fli\u011findeki veya daha k\u00fc\u00e7\u00fck ekranlar i\u00e7in *\/\n @media (max-width: 768px) {\n .content-wrapper {\n padding: 10px;\n margin: 5px;\n font-size: 0.9em; \/* Yaz\u0131 boyutunu k\u00fc\u00e7\u00fclt *\/\n }\n }\n\n \/* 480px geni\u015fli\u011findeki veya daha k\u00fc\u00e7\u00fck ekranlar i\u00e7in *\/\n @media (max-width: 480px) {\n .content-wrapper {\n padding: 5px;\n margin: 0;\n font-size: 0.8em;\n border: none; \/* Kenarl\u0131k kald\u0131rma *\/\n }\n }\n<\/style>\n <\/pre>\n<p><\/code><\/p>\n<p>\n Bu CSS \u00f6rne\u011fi, bir <code>content-wrapper<\/code> s\u0131n\u0131f\u0131na sahip elementin farkl\u0131 ekran boyutlar\u0131nda nas\u0131l g\u00f6r\u00fcnece\u011fini ayarlar. SSE'nin kendisi mobil cihazlara \u00f6zg\u00fc ek kodlama gerektirmez, ancak mobil a\u011flardaki kesintilere kar\u015f\u0131 uygulamay\u0131 dayan\u0131kl\u0131 hale getirmek i\u00e7in sunucu ve istemci taraf\u0131 hata y\u00f6netimi ve yeniden ba\u011flanma stratejilerini iyi planlamak esast\u0131r.\n <\/p>\n<h2>Sonu\u00e7: Server-Sent Events: Modern Web Uygulamalar\u0131n\u0131n Gizli Kahraman\u0131<\/h2>\n<p>\n Ger\u00e7ek zamanl\u0131 web uygulamalar\u0131 \u00e7a\u011f\u0131nda, sunucudan istemciye s\u00fcrekli ve anl\u0131k veri ak\u0131\u015f\u0131 sa\u011flamak vazge\u00e7ilmez bir gereklilik haline gelmi\u015ftir. Bu ihtiyac\u0131 kar\u015f\u0131lamak i\u00e7in akla gelen ilk \u00e7\u00f6z\u00fcm genellikle WebSockets olsa da, bu makalede Server-Sent Events (SSE) adl\u0131, \u00e7o\u011fu zaman hak etti\u011finden daha az ilgi g\u00f6ren bir alternatifi detayl\u0131ca inceledik. SSE'nin, WebSockets'in sundu\u011fu \u00e7ift y\u00f6nl\u00fc ileti\u015fim karma\u015f\u0131kl\u0131\u011f\u0131na ihtiya\u00e7 duymayan tek y\u00f6nl\u00fc veri ak\u0131\u015f\u0131 senaryolar\u0131 i\u00e7in ne kadar basit, verimli ve g\u00fc\u00e7l\u00fc bir \u00e7\u00f6z\u00fcm oldu\u011funu g\u00f6rd\u00fck. Canl\u0131 haber ak\u0131\u015flar\u0131, finansal verilerin takibi ve y\u00f6netici panellerindeki anl\u0131k metrik g\u00fcncellemeleri gibi ger\u00e7ek d\u00fcnya senaryolar\u0131nda, SSE'nin mevcut HTTP altyap\u0131s\u0131n\u0131 kullanarak nas\u0131l sorunsuz bir \u015fekilde entegre olabildi\u011fine tan\u0131k olduk.\n <\/p>\n<p>\n SSE, <code>EventSource<\/code> API'sinin otomatik yeniden ba\u011flanma \u00f6zelli\u011fi, basit metin tabanl\u0131 protokol\u00fc ve mevcut HTTP ara\u00e7lar\u0131yla uyumlulu\u011fu sayesinde geli\u015ftirme s\u00fcrecini \u00f6nemli \u00f6l\u00e7\u00fcde h\u0131zland\u0131r\u0131r ve operasyonel karma\u015f\u0131kl\u0131\u011f\u0131 azalt\u0131r. Y\u00fcksek performans ve \u00f6l\u00e7eklenebilirlik hedeflendi\u011finde ise HTTP\/2, y\u00fck dengeleyicilerle do\u011fru yap\u0131land\u0131rma ve sunucu taraf\u0131nda olaylar\u0131 y\u00f6netmek i\u00e7in ak\u0131ll\u0131 stratejiler gibi ileri d\u00fczey konular\u0131n g\u00f6z \u00f6n\u00fcnde bulundurulmas\u0131 gerekti\u011fini vurgulad\u0131k. G\u00fcvenlik, HTTPS ve do\u011fru kimlik do\u011frulama\/yetkilendirme mekanizmalar\u0131yla sa\u011flan\u0131rken, mobil uyumluluk ise <code>EventSource<\/code> API'sinin geni\u015f taray\u0131c\u0131 deste\u011fi ve otomatik yeniden ba\u011flanma yetenekleri sayesinde do\u011fal olarak elde edilir.\n <\/p>\n<p>\n \u00d6zetle, her ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131 ihtiyac\u0131n\u0131zda WebSockets'e y\u00f6nelmeden \u00f6nce, projenizin \u00e7ift y\u00f6nl\u00fc ileti\u015fime ger\u00e7ekten ihtiya\u00e7 duyup duymad\u0131\u011f\u0131n\u0131 sorgulaman\u0131z \u00f6nemlidir. E\u011fer sadece sunucudan istemciye veri \"itmek\" yeterliyse, Server-Sent Events, uygulaman\u0131z i\u00e7in \u00e7ok daha basit, hafif ve y\u00f6netilebilir bir alternatif sunabilir. Modern web uygulamalar\u0131n\u0131n geli\u015ftirme s\u00fcrecinde, do\u011fru arac\u0131 do\u011fru yerde kullanmak, hem geli\u015ftirme verimlili\u011fini art\u0131r\u0131r hem de nihai \u00fcr\u00fcn\u00fcn performans\u0131n\u0131 ve s\u00fcrd\u00fcr\u00fclebilirli\u011fini optimize eder. SSE'nin gizli kalm\u0131\u015f g\u00fcc\u00fcn\u00fc ke\u015ffetmeniz ve projelerinizde cesurca kullanman\u0131z dile\u011fiyle.\n <\/p>\n<h3>S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n<ul>\n<li>\n<h4>SSE sadece metin mi g\u00f6nderebilir?<\/h4>\n<p>Evet, Server-Sent Events (SSE) protokol\u00fc yaln\u0131zca metin tabanl\u0131 verileri iletmek i\u00e7in tasarlanm\u0131\u015ft\u0131r. Ancak, bu metin genellikle JSON format\u0131nda oldu\u011fu i\u00e7in karma\u015f\u0131k veri yap\u0131lar\u0131 kolayl\u0131kla g\u00f6nderilebilir ve istemci taraf\u0131nda JavaScript <code>JSON.parse()<\/code> ile \u00e7\u00f6z\u00fcmlenebilir.<\/p>\n<\/li>\n<li>\n<h4>SSE taray\u0131c\u0131 uyumlulu\u011fu nas\u0131l?<\/h4>\n<p>SSE, modern taray\u0131c\u0131lar\u0131n (Chrome, Firefox, Safari, Edge) b\u00fcy\u00fck \u00e7o\u011funlu\u011fu taraf\u0131ndan \u00e7ok iyi desteklenmektedir. Internet Explorer taraf\u0131ndan desteklenmez, ancak eski taray\u0131c\u0131lar i\u00e7in bir polyfill kullanma se\u00e7ene\u011fi mevcuttur. Genel olarak, taray\u0131c\u0131 deste\u011fi konusunda endi\u015felenmenize gerek yoktur.<\/p>\n<\/li>\n<li>\n<h4>SSE ile ayn\u0131 anda ka\u00e7 ba\u011flant\u0131 desteklenebilir?<\/h4>\n<p>Desteklenebilecek e\u015fzamanl\u0131 SSE ba\u011flant\u0131lar\u0131n\u0131n say\u0131s\u0131 sunucunuzun kaynaklar\u0131na (CPU, bellek, dosya tan\u0131t\u0131c\u0131lar\u0131) ve i\u015fletim sisteminizin limitlerine ba\u011fl\u0131d\u0131r. Her a\u00e7\u0131k ba\u011flant\u0131, sunucuda bir miktar kaynak t\u00fcketir. Modern sunucular ve optimize edilmi\u015f yap\u0131land\u0131rmalarla on binlerce e\u015fzamanl\u0131 ba\u011flant\u0131 desteklenebilir, ancak \u00e7ok y\u00fcksek say\u0131lar i\u00e7in \u00f6zel optimizasyonlar ve mimariler (HTTP\/2, y\u00fck dengeleyiciler, mesaj kuyruklar\u0131) gerekebilir. Varsay\u0131lan olarak, \u00e7o\u011fu taray\u0131c\u0131 ayn\u0131 anda ayn\u0131 alan ad\u0131na en fazla 6-8 a\u00e7\u0131k SSE\/HTTP ba\u011flant\u0131s\u0131na izin verir.<\/p>\n<\/li>\n<li>\n<h4>G\u00fcvenlik konusunda nelere dikkat etmeliyim?<\/h4>\n<p>SSE ba\u011flant\u0131lar\u0131 i\u00e7in her zaman HTTPS kullan\u0131n. Ayr\u0131ca, SSE endpoint'lerinizi di\u011fer HTTP endpoint'leriniz gibi kimlik do\u011frulama (authentication) ve yetkilendirme (authorization) mekanizmalar\u0131yla koruyun. Yaln\u0131zca yetkili kullan\u0131c\u0131lar\u0131n belirli veri ak\u0131\u015flar\u0131na eri\u015febildi\u011finden emin olun ve Cross-Origin Resource Sharing (CORS) ba\u015fl\u0131klar\u0131n\u0131 do\u011fru yap\u0131land\u0131r\u0131n.<\/p>\n<\/li>\n<li>\n<h4>SSE kullan\u0131rken sunucu taraf\u0131nda hangi dilleri tercih edebilirim?<\/h4>\n<p>SSE ak\u0131\u015f\u0131 olu\u015fturmak i\u00e7in herhangi bir sunucu taraf\u0131 programlama dilini kullanabilirsiniz (Node.js, Python, PHP, Ruby, Java, Go vb.). \u00d6nemli olan, HTTP yan\u0131t ba\u015fl\u0131klar\u0131n\u0131 (<code>Content-Type: text\/event-stream<\/code> gibi) do\u011fru \u015fekilde ayarlamak ve verileri belirli bir formatta (<code>data: ...\\n\\n<\/code>) yazabilmektir. Bu makaledeki \u00f6rnekte Node.js kullan\u0131lm\u0131\u015f olsa da, mant\u0131k di\u011fer diller i\u00e7in de benzerdir.<\/p>\n<\/li>\n<\/ul>\n<p><\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve…","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[874],"tags":[],"class_list":{"0":"post-31363","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-server","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>WebSockets'e Gerek Kalmayabilir: Server-Sent Events'in Basit G\u00fcc\u00fc<\/title>\n<meta name=\"description\" content=\"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve anl\u0131k analiz g\u00f6sterge tablolar\u0131 gibi bir\u00e7ok senaryo, sunucudan istemciye ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 gerektiriyor. Bu ihtiya\u00e7 akla ilk olarak genellikle WebSockets teknolojisini getirir; \u00e7ift y\u00f6nl\u00fc, tam dubleks bir ileti\u015fim kanal\u0131 sunmas\u0131yla tan\u0131n\u0131r. Ancak, her ger\u00e7ek zamanl\u0131 veri ihtiyac\u0131nda WebSockets kullanmak ger\u00e7ekten en iyi \u00e7\u00f6z\u00fcm m\u00fcd\u00fcr? Genellikle g\u00f6z ard\u0131 edilen, daha basit ve daha verimli bir alternatif olan Server-Sent Events (SSE), belirli kullan\u0131m durumlar\u0131nda m\u00fckemmel bir se\u00e7enek olabilir. Bu makalede, WebSockets'in karma\u015f\u0131kl\u0131\u011f\u0131na girmeden, tek y\u00f6nl\u00fc ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 nas\u0131l kolayca sa\u011flayabilece\u011fimizi ve Server-Sent Events'in g\u00fcc\u00fcn\u00fc ke\u015ffedece\u011fiz. WebSockets'e k\u0131yasla daha az kaynak t\u00fcketen ve daha kolay y\u00f6netilebilen SSE, \u00f6zellikle sunucudan istemciye s\u00fcrekli bilgi ak\u0131\u015f\u0131 gerektiren uygulamalar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu teknik, istemcilerin sunucuya s\u00fcrekli istek g\u00f6nderme (polling) ihtiyac\u0131n\u0131 ortadan kald\u0131rarak a\u011f trafi\u011fini ve sunucu y\u00fck\u00fcn\u00fc azalt\u0131r. Dahas\u0131, taray\u0131c\u0131lar\u0131n yerle\u015fik EventSource API'si sayesinde kullan\u0131m\u0131 olduk\u00e7a basittir, bu da geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WebSockets'e Gerek Kalmayabilir: Server-Sent Events'in Basit G\u00fcc\u00fc\" \/>\n<meta property=\"og:description\" content=\"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve anl\u0131k analiz g\u00f6sterge tablolar\u0131 gibi bir\u00e7ok senaryo, sunucudan istemciye ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 gerektiriyor. Bu ihtiya\u00e7 akla ilk olarak genellikle WebSockets teknolojisini getirir; \u00e7ift y\u00f6nl\u00fc, tam dubleks bir ileti\u015fim kanal\u0131 sunmas\u0131yla tan\u0131n\u0131r. Ancak, her ger\u00e7ek zamanl\u0131 veri ihtiyac\u0131nda WebSockets kullanmak ger\u00e7ekten en iyi \u00e7\u00f6z\u00fcm m\u00fcd\u00fcr? Genellikle g\u00f6z ard\u0131 edilen, daha basit ve daha verimli bir alternatif olan Server-Sent Events (SSE), belirli kullan\u0131m durumlar\u0131nda m\u00fckemmel bir se\u00e7enek olabilir. Bu makalede, WebSockets'in karma\u015f\u0131kl\u0131\u011f\u0131na girmeden, tek y\u00f6nl\u00fc ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 nas\u0131l kolayca sa\u011flayabilece\u011fimizi ve Server-Sent Events'in g\u00fcc\u00fcn\u00fc ke\u015ffedece\u011fiz. WebSockets'e k\u0131yasla daha az kaynak t\u00fcketen ve daha kolay y\u00f6netilebilen SSE, \u00f6zellikle sunucudan istemciye s\u00fcrekli bilgi ak\u0131\u015f\u0131 gerektiren uygulamalar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu teknik, istemcilerin sunucuya s\u00fcrekli istek g\u00f6nderme (polling) ihtiyac\u0131n\u0131 ortadan kald\u0131rarak a\u011f trafi\u011fini ve sunucu y\u00fck\u00fcn\u00fc azalt\u0131r. Dahas\u0131, taray\u0131c\u0131lar\u0131n yerle\u015fik EventSource API'si sayesinde kullan\u0131m\u0131 olduk\u00e7a basittir, bu da geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-09T00:31:18+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"25 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"WebSockets’e Gerek Kalmayabilir: Server-Sent Events’in Basit G\u00fcc\u00fc\",\"datePublished\":\"2025-10-09T00:31:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\"},\"wordCount\":4720,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Server\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\",\"name\":\"WebSockets'e Gerek Kalmayabilir: Server-Sent Events'in Basit G\u00fcc\u00fc\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-09T00:31:18+00:00\",\"description\":\"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve anl\u0131k analiz g\u00f6sterge tablolar\u0131 gibi bir\u00e7ok senaryo, sunucudan istemciye ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 gerektiriyor. Bu ihtiya\u00e7 akla ilk olarak genellikle WebSockets teknolojisini getirir; \u00e7ift y\u00f6nl\u00fc, tam dubleks bir ileti\u015fim kanal\u0131 sunmas\u0131yla tan\u0131n\u0131r. Ancak, her ger\u00e7ek zamanl\u0131 veri ihtiyac\u0131nda WebSockets kullanmak ger\u00e7ekten en iyi \u00e7\u00f6z\u00fcm m\u00fcd\u00fcr? Genellikle g\u00f6z ard\u0131 edilen, daha basit ve daha verimli bir alternatif olan Server-Sent Events (SSE), belirli kullan\u0131m durumlar\u0131nda m\u00fckemmel bir se\u00e7enek olabilir. Bu makalede, WebSockets'in karma\u015f\u0131kl\u0131\u011f\u0131na girmeden, tek y\u00f6nl\u00fc ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 nas\u0131l kolayca sa\u011flayabilece\u011fimizi ve Server-Sent Events'in g\u00fcc\u00fcn\u00fc ke\u015ffedece\u011fiz. WebSockets'e k\u0131yasla daha az kaynak t\u00fcketen ve daha kolay y\u00f6netilebilen SSE, \u00f6zellikle sunucudan istemciye s\u00fcrekli bilgi ak\u0131\u015f\u0131 gerektiren uygulamalar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu teknik, istemcilerin sunucuya s\u00fcrekli istek g\u00f6nderme (polling) ihtiyac\u0131n\u0131 ortadan kald\u0131rarak a\u011f trafi\u011fini ve sunucu y\u00fck\u00fcn\u00fc azalt\u0131r. Dahas\u0131, taray\u0131c\u0131lar\u0131n yerle\u015fik EventSource API'si sayesinde kullan\u0131m\u0131 olduk\u00e7a basittir, bu da geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"WebSockets’e Gerek Kalmayabilir: Server-Sent Events’in Basit G\u00fcc\u00fc\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"WebSockets'e Gerek Kalmayabilir: Server-Sent Events'in Basit G\u00fcc\u00fc","description":"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve anl\u0131k analiz g\u00f6sterge tablolar\u0131 gibi bir\u00e7ok senaryo, sunucudan istemciye ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 gerektiriyor. Bu ihtiya\u00e7 akla ilk olarak genellikle WebSockets teknolojisini getirir; \u00e7ift y\u00f6nl\u00fc, tam dubleks bir ileti\u015fim kanal\u0131 sunmas\u0131yla tan\u0131n\u0131r. Ancak, her ger\u00e7ek zamanl\u0131 veri ihtiyac\u0131nda WebSockets kullanmak ger\u00e7ekten en iyi \u00e7\u00f6z\u00fcm m\u00fcd\u00fcr? Genellikle g\u00f6z ard\u0131 edilen, daha basit ve daha verimli bir alternatif olan Server-Sent Events (SSE), belirli kullan\u0131m durumlar\u0131nda m\u00fckemmel bir se\u00e7enek olabilir. Bu makalede, WebSockets'in karma\u015f\u0131kl\u0131\u011f\u0131na girmeden, tek y\u00f6nl\u00fc ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 nas\u0131l kolayca sa\u011flayabilece\u011fimizi ve Server-Sent Events'in g\u00fcc\u00fcn\u00fc ke\u015ffedece\u011fiz. WebSockets'e k\u0131yasla daha az kaynak t\u00fcketen ve daha kolay y\u00f6netilebilen SSE, \u00f6zellikle sunucudan istemciye s\u00fcrekli bilgi ak\u0131\u015f\u0131 gerektiren uygulamalar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu teknik, istemcilerin sunucuya s\u00fcrekli istek g\u00f6nderme (polling) ihtiyac\u0131n\u0131 ortadan kald\u0131rarak a\u011f trafi\u011fini ve sunucu y\u00fck\u00fcn\u00fc azalt\u0131r. Dahas\u0131, taray\u0131c\u0131lar\u0131n yerle\u015fik EventSource API'si sayesinde kullan\u0131m\u0131 olduk\u00e7a basittir, bu da geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/","og_locale":"tr_TR","og_type":"article","og_title":"WebSockets'e Gerek Kalmayabilir: Server-Sent Events'in Basit G\u00fcc\u00fc","og_description":"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve anl\u0131k analiz g\u00f6sterge tablolar\u0131 gibi bir\u00e7ok senaryo, sunucudan istemciye ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 gerektiriyor. Bu ihtiya\u00e7 akla ilk olarak genellikle WebSockets teknolojisini getirir; \u00e7ift y\u00f6nl\u00fc, tam dubleks bir ileti\u015fim kanal\u0131 sunmas\u0131yla tan\u0131n\u0131r. Ancak, her ger\u00e7ek zamanl\u0131 veri ihtiyac\u0131nda WebSockets kullanmak ger\u00e7ekten en iyi \u00e7\u00f6z\u00fcm m\u00fcd\u00fcr? Genellikle g\u00f6z ard\u0131 edilen, daha basit ve daha verimli bir alternatif olan Server-Sent Events (SSE), belirli kullan\u0131m durumlar\u0131nda m\u00fckemmel bir se\u00e7enek olabilir. Bu makalede, WebSockets'in karma\u015f\u0131kl\u0131\u011f\u0131na girmeden, tek y\u00f6nl\u00fc ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 nas\u0131l kolayca sa\u011flayabilece\u011fimizi ve Server-Sent Events'in g\u00fcc\u00fcn\u00fc ke\u015ffedece\u011fiz. WebSockets'e k\u0131yasla daha az kaynak t\u00fcketen ve daha kolay y\u00f6netilebilen SSE, \u00f6zellikle sunucudan istemciye s\u00fcrekli bilgi ak\u0131\u015f\u0131 gerektiren uygulamalar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu teknik, istemcilerin sunucuya s\u00fcrekli istek g\u00f6nderme (polling) ihtiyac\u0131n\u0131 ortadan kald\u0131rarak a\u011f trafi\u011fini ve sunucu y\u00fck\u00fcn\u00fc azalt\u0131r. Dahas\u0131, taray\u0131c\u0131lar\u0131n yerle\u015fik EventSource API'si sayesinde kullan\u0131m\u0131 olduk\u00e7a basittir, bu da geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.","og_url":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-09T00:31:18+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"25 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"WebSockets’e Gerek Kalmayabilir: Server-Sent Events’in Basit G\u00fcc\u00fc","datePublished":"2025-10-09T00:31:18+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/"},"wordCount":4720,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Server"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/","url":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/","name":"WebSockets'e Gerek Kalmayabilir: Server-Sent Events'in Basit G\u00fcc\u00fc","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-09T00:31:18+00:00","description":"Modern web uygulamalar\u0131, kullan\u0131c\u0131lara anl\u0131k ve dinamik bir deneyim sunma aray\u0131\u015f\u0131nda. Canl\u0131 sohbetler, borsa takipleri, bildirim ak\u0131\u015flar\u0131 ve anl\u0131k analiz g\u00f6sterge tablolar\u0131 gibi bir\u00e7ok senaryo, sunucudan istemciye ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 gerektiriyor. Bu ihtiya\u00e7 akla ilk olarak genellikle WebSockets teknolojisini getirir; \u00e7ift y\u00f6nl\u00fc, tam dubleks bir ileti\u015fim kanal\u0131 sunmas\u0131yla tan\u0131n\u0131r. Ancak, her ger\u00e7ek zamanl\u0131 veri ihtiyac\u0131nda WebSockets kullanmak ger\u00e7ekten en iyi \u00e7\u00f6z\u00fcm m\u00fcd\u00fcr? Genellikle g\u00f6z ard\u0131 edilen, daha basit ve daha verimli bir alternatif olan Server-Sent Events (SSE), belirli kullan\u0131m durumlar\u0131nda m\u00fckemmel bir se\u00e7enek olabilir. Bu makalede, WebSockets'in karma\u015f\u0131kl\u0131\u011f\u0131na girmeden, tek y\u00f6nl\u00fc ger\u00e7ek zamanl\u0131 veri ak\u0131\u015f\u0131n\u0131 nas\u0131l kolayca sa\u011flayabilece\u011fimizi ve Server-Sent Events'in g\u00fcc\u00fcn\u00fc ke\u015ffedece\u011fiz. WebSockets'e k\u0131yasla daha az kaynak t\u00fcketen ve daha kolay y\u00f6netilebilen SSE, \u00f6zellikle sunucudan istemciye s\u00fcrekli bilgi ak\u0131\u015f\u0131 gerektiren uygulamalar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu teknik, istemcilerin sunucuya s\u00fcrekli istek g\u00f6nderme (polling) ihtiyac\u0131n\u0131 ortadan kald\u0131rarak a\u011f trafi\u011fini ve sunucu y\u00fck\u00fcn\u00fc azalt\u0131r. Dahas\u0131, taray\u0131c\u0131lar\u0131n yerle\u015fik EventSource API'si sayesinde kullan\u0131m\u0131 olduk\u00e7a basittir, bu da geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/websocketse-gerek-kalmayabilir-server-sent-eventsin-basit-gucu\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"WebSockets’e Gerek Kalmayabilir: Server-Sent Events’in Basit G\u00fcc\u00fc"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=31363"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31363\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=31363"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=31363"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=31363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}