New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite Play bridge in Scala #3

Closed
flowersinthesand opened this Issue Mar 20, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@flowersinthesand
Member

flowersinthesand commented Mar 20, 2015

Because the current implementation uses Play's Java API, the following features are missing in Play bridge. In other means, they would be supported probably with Play's Scala API.

  • Play Java API requires to fix the data type to be used in the connection both in HTTP and WebSocket. It's not a problem in PlayServerHttpExchange, but in PlayServerWebSocket, text frame and binary frame can't be used together in a single connection.
  • Play doesn't support reading request asynchronously but I'm not sure Scala API can help it.
  • With Java API, a user have to use internal API which has been changed even in patch release. Scala API may solve that issue as well. (Maybe using Scala implementation and Java wrapper API just like Play framework itself)

New implementation should have unit tests and come with helper class making it easy to bridge application and Play. However, to make sure Java API's limit, we should contact their community first.

@flowersinthesand

This comment has been minimized.

Show comment
Hide comment
@flowersinthesand
Member

flowersinthesand commented Aug 1, 2015

This issue was moved to flowersinthesand/asity-play2#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment