When I first stumbled on the Internet over 20 years ago, I was very fond of all the diverse chat desktop applications that existed back then.
Years later I made my own just for nostalgia reasons:
https://www.youtube.com/watch?v=RudiPIGG7co
#clientserver
#Development #Explainers
What’s OAuth2 anyway? · How the most popular authorization framework works https://ilo.im/1623dq
_____
#Authorization #Authentication #Credentials #OAuth #OAuth2 #ClientServer #Security #WebDev #Frontend #Backend
SyncFramework for XPO: Updated for .NET 8 & 9 and DevExpress 24.2.3!
#dotnet8 #dotnet9 #devexpress #xpo #xaf #syncframework #datasynchronization #deltaencoding #nuget #csharp #databasesync #crossplatform #orm #datareplication #incrementalbackup #devexpressxpo #devexpressxaf #enterprisedevelopment #businessapplications #clientserver
Разбираемся с сетевым программированием на Rust
Язык программирования Rust стал достаточно популярен благодаря своей надежности, безопасности и производительности. В рамках данной статьи мы не будем подробно обсуждать преимущества данного языка, так как на эту тему уже написано много статей. Вместо этого мы рассмотрим разработку простейшего сетевого приложения, работающего по принципу клиент-сервер. Те читатели, кто уже знаком с Rust могут пропустить следующий раздел и сразу перейти к рассмотрению сетевого приложения. Ну а тем, кто совсем не знаком с этим языком предлагается установить необходимые инструменты и ознакомиться с базовыми конструкциями Rust.
[Перевод] Руководство по межпроцессному взаимодействию (IPC) в Linux — Часть 3
Представляю вашему вниманию третью (заключительную) часть перевода статьи A guide to inter-process communication in Linux . Первая часть перевода была посвящена общему введению в курс дела и механизму разделяемого хранилища (shared storage). Во второй части были рассмотрены механизмы каналов (именованных и неименованных) и очереди сообщений. В третьей части автор статьи ставит перед собой цель рассказать вам о сокетах и сигналах; подводит общие итоги по межпроцессному взаимодействию в Linux. Приятного чтения!
#Development
React is (becoming) a full-stack framework · It has bridged the gap between frontend and backend https://ilo.im/15zugx
_____
#Framework #React #JavaScript #TypeScript #RestAPI #NextJS #ClientServer #WebDev #Frontend #Backend
A Bit of Security for Feb 22, 2024
How we wrote the Client Server and Cooperative Processing research report – and why an LLM could never do it. Listen to this -
https://youtu.be/aVx1HW2jDKc
Let me know what you think in the comments below or at wjmalik@noc.social
#cybersecuritytips #LLMlimits #Clientserver #ntierapplications #BitofSec
With a lot of new client-side "frontend" tools available, what are your thoughts on switching to a #clientserver architecture, where the server-side is basically #serverless persistence and long-running processes (#sagas)?
#feditips #fediverse #clientserver honestly I don’t like the default mastodon app, but I haven’t found anything that’s any better. Don’t like manny, don’t care for mammoth, but still gonna try it out
2 minute excerpt from Hydration, recorded from practice on 12/11. This is some damn fine doom metal.
#Musodon #Doom #DoomMetal #HeavyBlackNoise #Tokyo #ClientServer
4 essential characteristics of successful APIs - For any external system/app to connect to a server system
If you are building an application that uses some variation of a client/server model, you need an application programming interface (API). An API is a clearly defined boundary between one process and another. A common boundary in web applications is a REST/JSON API.
An example of an API usage could be a police system that must verify if someone has a criminal record or not, for applying maybe for a liquor license business. Where paperwork was sent manually to the police to verify whether the liquor license applicant has a criminal record or not, could be replaced with an intersystem API call from the liquor licensing system, where the API receives an identity number, and only returns and true/false without exposing any personal details.
But some important characteristics must be designed into that API for it to be sure and to function correctly.
See 4 essential characteristics of successful APIs
https://opensource.com/article/21/5/successful-apis https://squeet.me/objects/962c3e108de34b11d36819457af9cbb2212222d9
Lately I find that the whole concept of #PeerToPeer vs #ClientServer models is kind of pointless. As long as the user controls their own data it doesn't matter how the system works.
That said, I do see that the two models work better in different scenarios. For instance, #Mastodon is way better as a server based system since you can easily form communities on it. Whereas, #Scuttlebutt is better for staying connected to people even without Internet Access. Diversity is a competitive advantage.
"we’ve been defaulted for more than 20 years to an #asymmetric #power #relationship between #people and #publishers called #clientserver.
It doesn’t have to be that way.
Beneath the #Web, the Net’s TCP/IP #protocol—the gravity that holds us all together in #cyberspace—remains no less #P2P and end-to-end than it was in the 1st place.
Meaning there is nothing to the Net that prevents each of us from having plenty of power on our own."
@dsearls
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst