I think thats not supported anymore, remember seeing something about it being legacy code flagged for removal (if it hasnt already been)
"You couldn't build brand new real-time applications on top of Wave." Not true; arwave.org (see vids) Sadly on hold till apache gets a client protocal
none of which federate with eachother :(
GWT reduces complexity for this sort of thing imho - the complexity comes more from the way the client and server code are tied all together, the rather excessive abstractions and factory processes, and some legacy…
I have been wanting to do this for ages...but without a established client/sever protocol its a nightmare. And GWT is fine, I love GWT, but the current codebase has the current client and sever tied together you cant…
I think thats not supported anymore, remember seeing something about it being legacy code flagged for removal (if it hasnt already been)
"You couldn't build brand new real-time applications on top of Wave." Not true; arwave.org (see vids) Sadly on hold till apache gets a client protocal
none of which federate with eachother :(
GWT reduces complexity for this sort of thing imho - the complexity comes more from the way the client and server code are tied all together, the rather excessive abstractions and factory processes, and some legacy…
I have been wanting to do this for ages...but without a established client/sever protocol its a nightmare. And GWT is fine, I love GWT, but the current codebase has the current client and sever tied together you cant…