Armagan Amcalar

That’s right. That’s also partially why we didn’t merge this. However, cote could still provide an easier interface for —for example— Express apps to hook into. Currently it requires a...

This is route/event based match up. There are multiple other ways possible, including having a single URL and then forwarding to different events based on POST parameters, or configuration when...

You don't have to use any http microframework style — this would just be an addition to how cote operates on its own. A separate wrapper or a plugin can...

Yes, that would be amazing. I can help if anyone wants to tackle it.

Yes, this should ideally be a middleware, with a little bit more magic to make sure you don’t have to include it in every single requester / responder / etc....

Hello, cote doesn't have an official Typescript support. I think the current typings come from `https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/cote/index.d.ts` — I'd recommend submitting a PR there to add redis connectivity options.

@Dalisra not `requests`, but `respondsTo`, is used for Sockend communication. It defines what a Sockend can pipe to the frontend.

cote doesn't currently allow transfer of binary files in a coherent way. It's not very easy to implement it, but still doable. I would love to have some help from...

Thanks a lot! JWT is totally possible, but would have to rely on custom implementation on your side — currently you can't prevent daemons from connecting to one another as...

I personally believe you can't solve security by throwing concepts at it. It is a conscious decision where and how you want to implement it, taking into consideration a lot...