is there a sample yada project out there that serves up static files?

I'm kinda stumped

oops I could do it with ->ResourcesMaybe in bidi

https://twitter.com/malcolmsparks/status/690471017945366528

@jethroksy: see here: https://yada.juxt.pro/dir/

if you have a directory of files called 'dir', you can serve them with (yada dir)

not sure it can be much simpler

Cool!!

there are various options you can give to static directory serving, see here: https://github.com/juxt/yada/blob/master/dev/src/yada/dev/talks.clj

Is this documented somewhere

https://yada.juxt.pro/user-manual.html#Example6:Fileserver

but it may be out-of-date

documentation is coming though, I am doing quite a lot of documenting these days

the user-manual is growing

That link says coming soon

sorry

scroll down a bit

but the talks example is the most up to date and you can run it

it's how this is implemented: https://yada.juxt.pro/talks/README.md

whereby .md files are automatically run through a markdown preprocessor

but other files are statically served

Ah okay I see it

using yada to serve these is far superior to bidi's ResourcesMaybe because you get all the caching and conditional request semantics, etc.

+ security and so on

Really cool stuff going on but its quite a departure from the usual compojure ring stack

until yada 1.1 is officially released, you'll have to dig into the code examples a little bit

yes, it's a big departure - partly because the compojure ring stack can't do async (see how pedestal had to depart from ring too)

My migration path was kinda hard

but you can mix-and-match - some resources you can keep as compojure, others you might serve with bidi/yada

I happened to be using aleph as a WS client so everything fit perfectly

I'll dig around

yes, are you doing it like this: https://yada.juxt.pro/talks/clojutre-2015.html#/slide-orgheadline40

sorry that example is a bit out of date but the point is you can return the promise that aleph client returns to you

it all just works, asynchronously

or should 😉

I am not unfortunately

But my connection is a record

The only protocols I extended were Components

I could probably try this and upload it as an example

Oh do SSEs support streams?

I've seen examples, but only with chan

what kind of stream are you looking to support?

you can support any stream that can be converted to a manifold source, so it should be easy

if yada doesn't support the exact type of stream you need, extend the yada.body.MessageBody protocol with your own implementation - you can see how the core.async channel is implemented and derive it from that

but if you tell me what kind of stream you need I'm happy to put it into the next release

@jethroksy: thanks for your points about the docs, it's on my list to look into to

just a bit busy with client work today

Just the raw manifold stream

It's just a question, have yet to try it

And you're welcome (: