hey guys, i'm interested in possibly refactoring an early stage api server away from ring, due to the lack of async support, and it feels a bit... chaotic

i see a great place for pedestal here, but my development environment is under windows, which i see is unsupported

what kind of level of "unsupported" is this? is it "it will not even compile"-unsupported, or "dont use it for production"-unsupported?

since we're already using vagrant, an option could be to run the entire dev environment in a vagrant box, but that would complicate the development process a lot i think

hey @lmergen pedestal ships with some ancillary .sh scripts, but there's nothing in the library that is OS specific.

ahhh so there's nothing to worry about really

that's great news

should not be

you should update the github Readme

yeah, agree, that should go into an issue

it kind of had me thinking it's currently not working. it should read something like "although we don't actively test it, it should work. blah blah"

yeah- there has been a flurry of activity in the repo recently, that would be good to clarify

i'll make sure to test it soon and if it works send in a PR for the Readme

that would be great!

what's the recommended way to run pedestal, if i'm planning on doing some async work? is jetty9 already supported?

it's been a while since i've looked but you should be able to write async interceptors and use non-blocking io with any container.

and yes the jetty adapter pulls in jetty 9