| Author |
Message |
|
| Guest |
 Posted: Thu Dec 17, 2009 9:06 pm |
 |
|
|
Guest
|
Hello all,
Does someone actually use yaws and the websocket feature introduced with HTML5 ?
Thank you
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Dec 17, 2009 9:38 pm |
|
|
|
Guest
|
wde wrote:
> Hello all,
>
> Does someone actually use yaws and the websocket feature introduced with HTML5 ?
>
Not to my knowledge, thus excellent opportunity to be the first !! and publish.
/klacke
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post received from mailinglist |
|
|
| Back to top |
|
| nesrait |
| Posted: Thu Dec 17, 2009 11:23 pm |
|
|
|
User
Joined: 02 May 2009
Posts: 33
Location: Portugal
|
Hi all,
Just uploaded a Web Sockets ewgi implementation that is working on Yaws, Mochiweb and Inets.
To use it just grab the last code from:
http://github.com/davide/ewgi |
|
|
| Back to top |
 
|
| Guest |
| Posted: Fri Dec 18, 2009 6:12 am |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 2:18 pm |
|
|
|
Guest
|
what about a new result type {websocket,Pid::pid(),Active::bool()} ?
|
|
|
| Back to top |
|
| nesrait |
| Posted: Fri Dec 18, 2009 2:26 pm |
|
|
|
User
Joined: 02 May 2009
Posts: 33
Location: Portugal
|
Hi again,
Both wde and me have stumbled in a strange behaviour: even after passing control over the socket to the new owner (I've checked that it succeeds in doing so) the Yaws process is still able to close the socket - taking away all the funin web socketing. :\
Additionally, I should notice that my ewgi code only seems to work on mochiweb, the same issue pops up on ewgi_yaws and ewgi_inets. In both cases, simply delaying the "killing" of the server process seems to be enough to have the web socket open/working.
My current assumption is that it is possible for another process that is not the socket owner to close it. Can anyone share some insights into this?
Now excuse me while I go fire my test monkey. 
Cheers,
Davide
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 2:31 pm |
|
|
|
Guest
|
Your code seems good for me davide (but I'm not a guru)
|
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 3:14 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 3:27 pm |
|
|
|
Guest
|
Maybe we could add the Origin header in the yaws:http_collect_headers/4
|
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 3:29 pm |
|
|
|
Guest
|
|
| Back to top |
|
| nesrait |
| Posted: Fri Dec 18, 2009 3:30 pm |
|
|
|
User
Joined: 02 May 2009
Posts: 33
Location: Portugal
|
I just looked at the code and I suggest this:
case yaws:outh_get_doclose() of
|
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 3:38 pm |
|
|
|
Guest
|
seems better
|
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 3:48 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Fri Dec 18, 2009 3:50 pm |
|
|
|
Guest
|
2009/12/18 Steve Vinoski <vinoski@ieee.org (vinoski@ieee.org)>
Quote:
2009/12/18 Davide Marqu |
|
|
| Back to top |
|
| nesrait |
| Posted: Fri Dec 18, 2009 3:54 pm |
|
|
|
User
Joined: 02 May 2009
Posts: 33
Location: Portugal
|
Quote: Quote:
In that case, you could just return
{header, {connection, erase}}
in the same list where you return streamcontent_from_pid, which removes any Connection header from the reply headers and also sets doclose in the process registry to false.
Just to clarify, I will make the streamcontent_from_pid return value enforce this side-effect for the connection header and setting, but if you want it to work immediately you could put it in your code right now and it would still work even after I change the code.
Something like this?
handle_out_reply({websocket, _OwnerPid, _SocketMode}=Reply,
|
|
|
| Back to top |
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
