Thin reactive framework to provide and consume REST services
People
Repo info
Activity
William Boxhall
@williamboxhall
things I still wanna do
a) make Zoot compatible with the twitter Future so we dont' have to do that ugliness we discussed before
b) add some filter-chain stuff, authentication in the frontend then passing user session headers around
c) add some more fun endpoints
d) maybe tweak the Builder class I created. Maybe we should add it to Zoot, or allow Zoot to build client/server with nice defaults, just supplying host/port
Flavio W. Brasil
@fwbrasil
Cool stuff man! I'll check it out tomorrow
William Boxhall
@williamboxhall
@fwbrasil it seems that Zoot does not support having multiple "controllers" per service. I supply only one controller to new FinagleServer(Server[MyController](myController))
it would be nice to be able to go new FinagleServer(firstController, secondController, third...). For example my service has multiple REST resources that I wish to express as different Api traits
Flavio W. Brasil
@fwbrasil
Yeah, that's a bad limitation
The idea was mix all.traits together in only one api class
But I don't like this approach anymore
William Boxhall
@williamboxhall
I'm trying to wedge support for com.twitter.util.Future in to Zoot
think im in a bit over my head, but what the hey
William Boxhall
@williamboxhall
@fwbrasil is there an easy way for me to run the Zoot-Sample?
actually maybe it's just easier if i publish zoot locally and point my own sample project at it
William Boxhall
@williamboxhall
damn
@fwbrasil seems to swallow exception messages, makes it difficult to debug
William Boxhall
@williamboxhall
i think
actually its something wrong with my sample project swallowing errors