- Jun 6, 2020
- 11,593
- 4,508
so, there's something called server side events (SSE).
it apparently has something to do with notifications
from a web server to a browser. i'm guessing it's what
happens when you see an annoying pop-up message
from a web server asking persmission to send you
notifications. good luck with that; not!
i noticed a thread earlier in the week relating to
server side events (SSE), but for b4j.
anyway, the thing is: mirabile dictu! it works with okhttputils2.
that is, it doesn't interfere with okhttputils2 (at least not that
i have seen); you can do your normal okhttputils2 business
at 1 url while still receiving notifications from a totally
different url. wait, what? for example, if you had a website
that sent periodic world cup updates as notifications, you could
receive them while downloading jpg's or updating your mysql
database on another url. win-win, right?
so, for what it's worth, i put it out there. i tested it with a
website that allows test sse connections...
it apparently has something to do with notifications
from a web server to a browser. i'm guessing it's what
happens when you see an annoying pop-up message
from a web server asking persmission to send you
notifications. good luck with that; not!
i noticed a thread earlier in the week relating to
server side events (SSE), but for b4j.
anyway, the thing is: mirabile dictu! it works with okhttputils2.
that is, it doesn't interfere with okhttputils2 (at least not that
i have seen); you can do your normal okhttputils2 business
at 1 url while still receiving notifications from a totally
different url. wait, what? for example, if you had a website
that sent periodic world cup updates as notifications, you could
receive them while downloading jpg's or updating your mysql
database on another url. win-win, right?
so, for what it's worth, i put it out there. i tested it with a
website that allows test sse connections...
برای دیدن لینک ها باید ثبت نام کنید
برای دیدن لینک ها باید ثبت نام کنید