faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
<FromGitter> <robacarp> @sdzyba the trick is that the compiler doesn’t know that halt! Does what it does
<FromGitter> <robacarp> I typically do `return halt! 404` and that works
_whitelogger has joined #amber
<FromGitter> <sdzyba> @robacarp thanks
_whitelogger has joined #amber
<FromGitter> <valamorgon> is it logical to send images through websocket if client is already connected to websocket? or should I notify client that there is a new image that he should fetch, and he will fetch it seperately?
<robacarp> I tend to favor using websockets for signaling only, and resource fetching to be done over rest
<robacarp> but I think it's personal preference
<FromGitter> <drujensen> Same here