Mario Kušek

3K posts

Mario Kušek

Mario Kušek

@MarioKusek

My field interests are: #IoT #java #programming #springBoot #TDD #distributedSystems #microservices #eventmodeling #edgecomputing

Zagreb, Croatia Katılım Ağustos 2010
299 Takip Edilen185 Takipçiler
Mario Kušek retweetledi
IoTLabFER
IoTLabFER@IoTLabFER·
🚀 AI Meets the Physical World: #AIoT in Action with #AIoTwin! Discover how AI integrated into Cloud-Edge-IoT (CEI) systems is redefining real-time intelligence — from city traffic to smart industry. 🌐🤖
English
1
2
3
19
Mario Kušek retweetledi
Bernard Traversat
Bernard Traversat@BTraTra·
30 years ago today, the first version of Java was released. Java has become a cornerstone of modern computing. This incredible journey wouldn’t have been possible without the passionate people who’ve built this technology and contributed to this vibrant community. Thank you all!
Bernard Traversat tweet media
English
0
5
40
2.3K
Dan Vega
Dan Vega@therealdanvega·
The Spring Initializr now has a Bookmarks feature 🔥
English
4
11
71
3.6K
Mario Kušek retweetledi
JUnit Team 💙💛
JUnit Team 💙💛@junitteam·
#JUnit 5.11 is released! 🏟 FieldSource for param. tests ✨ Dynamic/param. test enhancements 🧹 AutoClose for test fields 🤖 ConversionSupport utility 💡 Extensible syntax for discovery selectors 🌀 Before/AfterSuite 🐞 Field/method search bug fixes junit.org/junit5/docs/5.…
English
0
35
109
8.1K
Mario Kušek
Mario Kušek@MarioKusek·
@alexboly I totally agree with you. As @unclebobmartin said either we will do our jobs professionally (you said grow up and take responsibility) or someone will regulate our job and impose rules that we will have to follow. Unfortunately I think we will be regulated.
English
0
0
0
16
Mario Kušek
Mario Kušek@MarioKusek·
@awkwardgoogle Game similar to space invaders which I need to type in Sinclair ZX81 when I wanted to play. The code was published in local (Croatia/Yugoslavia) magazine. I think it was in 1983
English
0
0
0
48
Adam Ruka
Adam Ruka@adam_ruka·
I just released version 1.5 of Jilt, my open-source Java library for automatically-generating Builder classes! Thanks to @alex_j_navarro, @AurelienMino and Diego Pedregal for their contributions! github.com/skinny85/jilt Detailed release notes are in the next Tweet 👇
English
2
9
24
3.4K
Mario Kušek retweetledi
Java
Java@java·
Java users on macOS 14 running on Apple silicon systems should consider delaying the update to macOS 14.4. For further information: social.ora.cl/6018kbMIo
English
14
314
579
255.9K
Mario Kušek retweetledi
Cory House
Cory House@housecor·
Problem: You want to get the last item in the array in JavaScript. Solution: Array .at.
Cory House tweet media
English
74
89
1.1K
136.8K
Mario Kušek retweetledi
IoTLabFER
IoTLabFER@IoTLabFER·
New publication 📯 The paper "A Multi-Agent System for Service Provisioning in an Internet-of-Things Smart Space Based on User Preferences​" was published in the open access journal @Sensors_MDPI! Find out more on the IoT4us project website: #news_131857" target="_blank" rel="nofollow noopener">iot4us.fer.hr/iot4us/en/news…
IoTLabFER tweet media
English
0
1
2
231
Mario Kušek
Mario Kušek@MarioKusek·
@bytebytego @alexxubyte Another question. How YouTube server in steps 9-… knows for which user it needs to ask that the user is authenticated?
English
1
0
0
640
Bytebytego
Bytebytego@bytebytego·
What is SSO (Single Sign-On)? Single Sign-On (SSO) is an authentication scheme. It allows a user to log in to different systems using a single ID. The diagram below illustrates how SSO works. Step 1: A user visits Gmail, or any email service. Gmail finds the user is not logged in and so redirects them to the SSO authentication server, which also finds the user is not logged in. As a result, the user is redirected to the SSO login page, where they enter their login credentials. Steps 2-3: The SSO authentication server validates the credentials, creates the global session for the user, and creates a token. Steps 4-7: Gmail validates the token in the SSO authentication server. The authentication server registers the Gmail system, and returns “valid.” Gmail returns the protected resource to the user. Step 8: From Gmail, the user navigates to another Google-owned website, for example, YouTube. Steps 9-10: YouTube finds the user is not logged in, and then requests authentication. The SSO authentication server finds the user is already logged in and returns the token. Step 11-14: YouTube validates the token in the SSO authentication server. The authentication server registers the YouTube system, and returns “valid.” YouTube returns the protected resource to the user. The process is complete and the user gets back access to their account. Over to you: Question 1: have you implemented SSO in your projects? What is the most difficult part? Question 2: what’s your favorite sign-in method and why? – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/3KCnWXq
Bytebytego tweet media
English
9
182
734
46.2K