#2876 Web Server API

Jed Tue 6 Sep

The wisp API is not very intuitive. Is there a framework that registers paths with closures.

main() {
  WispService {
    port = 8080
    GET("/app") |req, res| {

Henry Tue 6 Sep

Hi Jed,

You may find afBedsheet a useful alternative to the Wisp API.

SlimerDude Tue 6 Sep

Hi Jed,

I know the draft library registers paths with Methods (which is a step closer) - see the draft GitHub page for example usage and documentation.

Other than that, I think you'll have to write your own framework... :(

andy Tue 6 Sep

Doesn't use closures - but if you're feeling adventurous you can poke around Helix :)

SlimerDude Tue 6 Sep

I know this is hi-jacking a thread (sorry), but andy, I have to ask - what's fass!?

What are your requirements and future plans for fass?

I've been thinking of writing similar myself, but have my own requirements with regards to nested definitions, CSS variables, and cross-project/pod compilation. (Currently I'm using afSass4f in a pre-compilation stage.)

I don't want to re-invent the wheel if I can help it, so would fass be open to feature requests and pull requests?

andy Tue 6 Sep

That one's still cooking in the oven a bit :)

It can be used standalone - but really, helix + fanbars + fass are designed to work together as a cohesive framework and build workflow.

My internal use cases are driving all that right now, but once things stabilize, yes, open to PRs.

Login or Signup to reply.