URLs should be able to include HTTP verbs and headers.
They say "URLs define the "what" not the "how"" but protocol prefixes, file extensions, and query parameters are part of the how and yet they all exist in the URL.
Leaving HTTP verbs and headers out of URLs was an arbitrary decision.
#web #http #hypermedia #hateoas #webStandards #html #programming #networking
I just released version 2.1.4 of "JSON:API for Spring HATEOAS". This is a patch release with dependency updates to Spring Boot 3.5.0.
Det är en fröjd att arbeta med ett #API som följer #HATEOAS fullt ut. Jag slipper bläddra runt i källsystemet för att hitta rätt referenser eller rentav data som behövs för att färdigställa en komplex operation med flera anrop av olika typer som ska bli en del av lösningen. #livetSomITKonsult
I just released version 2.1.3 of "JSON:API for Spring HATEOAS". This is a bug fix release with dependency updates to the latest Spring libraries.
I just released version 2.1.2 of "JSON:API for Spring HATEOAS". This is a patch release with dependency updates to the latest Spring libraries.
New in "API Design Matters": "Wherefore HATEOAS", my views and commentary on Hypermedia APIs. https://apidesignmatters.substack.com/p/wherefore-hateoas
#APIDesignMatters #APIs #HATEOAS
People just like HTMX because it allows them use a language other than #JavaScript
There's no reason to use it if you like #JS
@colindean we used to be a proper #hypermedia!
@wyatt8740 I too used to apply #HATEOAS: anything accessible through URLs in HTML documents was fair game. That was until I encountered a whole captchalogue of methods that websites use to deter scraping.
1. #RateLimit per IPv4 address and /24 and publish no AAAA record for IPv6, with 24-hour fail2ban penalties for exceeding a limit
2. #CAPTCHA
3. #LoginWall (what Twitter tried and still uses in a scaled-back form)
I've seen quite a few intriguing links recently discussing "progressive web apps" (#PWA) as preferable to "single page apps" (SPA) and getting back to fundamental web technology (html and css) rather than frameworks.
Today I've bumped in to #htmx which argues for preferring hypermedia applications and emphasising #HATEOAS principles. It seems like a great fit with PWA.
Have been playing around with #HATEOAS
Thinking it as document synchronization (i.e alpine-ajax) make it easier to maintain than html swapping (i.e htmx). And, I ended up having less endpoints. It's kinda inconvenience because it based on html `id` and it needs to be unique. But that's why it's predictable.
Tips: some framework has useId(key) to generate html `id`. If not then you can do
```go
const myID = "ident-" + uuidv4() // global
```
How to GET a Cup of Coffee
https://www.infoq.com/articles/webber-rest-workflow/
Great article about self describing state machines with #REST
#hateoas #restful #linkingdata #linkrelations #semantics #semanticweb
