there's no doc around it, also I saw some where in SSE doc which mentioned it does not

how can I do that

Aleph supports websockets. They are not HTTP but an 'upgrade' protocol. Hence yada doesn't say much. See Aleph's docs

I see, thanks

https://datatracker.ietf.org/doc/draft-west-first-party-cookies/ better link on SameSite attribute. Looks like Mozilla were involved :thinking_face:. Don't know enough about IETF process to make judgement on it's viability as a standard. The expiration of nearly a year puts me off though.

https://bugzilla.mozilla.org/show_bug.cgi?id=795346 being pushed for impl...

When using yada.resources.classpath-resource/new-classpath-resource, it works fine with bidi.ring/make-handler routes, however once I switch to bidi.ring/make-handler routes handler (with a handler function which can return yada.yada/handler classpath-resource, it doesn't work. It it something to do with bidi's special protocols not working when using make-handler with a handler function?

Here's what I got to work: http://sprunge.us/PRdE Why would I have to have the handler twice? Perhaps the first one only does the bidi protocol stuff?

Admitedly my handler function could just act as an identity for cond :default.

@ghopper What happens if you do :default route?

@dominicm That seems to be working. :thumbsup:

@ghopper (yada/handler) turns a yada resource into a ring handler.

Just seems strange that the classpath resource needs to be in the routes and not just the handler.

It's because of the way you're handling it I think.

Because bidi.ring/make-handler needs the bidi/Matched stuff, I guess.

(From yada.bidi)

^^ you can do this

I could create my own bidi/Matched implementation?

absolutely, or bring in yada.bidi? 😉

yada.bidi has been brought in. My confusion was that yada.resources.classpath-resource wouldn't work when I gave it in the handler function.

It has to be in the routes and the handler.

Even with a [true :public] entry in routes and a :default (new-classpath-resource...) in the handler, it wouldn't work.

I'm a little confused by your case function

cond?

or cond, yeah. Why is it there?

Basically for /api it sends a 200 and an api resposne, and for misc other matching routes, which are defined elsewhere, it'll do some SSR stuff.

Then for resources, it should return those.

The whole issue is that those other misc routes need to be defined elsewhere and included here.

It's more that, I've never seen a cond in use. Oh, it's because you're using :keywords

Oh, basically it's just pairs of if-else's. Each lines starts with a conditional check, then the second expression is what should be done if that conditional is true.

I should be clearer. I've never actually needed to use a cond for this sort of purpose. Normally I have bidi resolve to a handler directly.

Oh, sorry... my bad. 😛 I almost always do as well; the reason I'm trying to here is because of those co-located other routes, which will always be keywords, so I need a handler function to translate those keywords into handlers.