[Pianod] web client how to?

[Peter Li]

Just as a heads up, I'm having issues with WSGW on RasPi.  It works fine on Fedora.  When I build and run on RasPi everything seems to be working.  When I try to connect to RasPi from the web client I seem to get all the right log messages from WSGW (running with -h -l):

1970-01-04 06:26:33: 17481: Header: GET /pianod?encoding=text HTTP/1.1
1970-01-04 06:26:33: 17481: Header: Upgrade: websocket
1970-01-04 06:26:33: 17481: Header: Connection: Upgrade
1970-01-04 06:26:33: 17481: Header: Host: 192.168.0.110:8000
1970-01-04 06:26:33: 17481: Header: Origin: http://deviousfish.com
1970-01-04 06:26:33: 17481: Header: Pragma: no-cache
1970-01-04 06:26:33: 17481: Header: Cache-Control: no-cache
1970-01-04 06:26:33: 17481: Header: Sec-WebSocket-Key: [excised]
1970-01-04 06:26:33: 17481: Header: Sec-WebSocket-Version: 13
1970-01-04 06:26:33: 17481: Header: Sec-WebSocket-Extensions: x-webkit-deflate-frame

But the web client says "Connection failed" instead of showing the control panels.

The timestamps above are funny because my ALARM box doesn't have network clock set up, but I get the same behavior from my Raspbian box where the timestamps look fine.

I'll debug more, probably next week, just thought I'd mention it.
P



On Feb 3, 2013, at 11:49 AM, Peter Li wrote:

> Thanks!  It works :)!
> 
> WSGW does build with IP6 now.  I still get an implicit declaration of arc4random, which I think needs some BSD header, but that's the only complaint at compile time now.  I'm not clear on the right way to fold the BSD stuff in; seems like it can cause conflicts?
> 
> Then I can start pianod, start wsgw, and use the deviousfish web client to control my pianod; nice!
> 
> A few funny things.  When I start wsgw I get:
> setup_ip6_socket: bind: Address already in use
> But there isn't anything there and it still works.  I get this on most ports.  If I try 80, which also doesn't have anything on this machine, then it won't let me do it at all.  I've gotten that message in other contexts too; is it because the port number has a different standard service?  Or firewall thing?
> 
> Also, after I disconnect from wsgw I have a [wsgw] <defunct> process hanging around.
> 
> Still, very cool; too bad the Android browser can't do websockets yet.  I'll try it in Firefox for Android.  And will try on the RasPis now too (was using my Fedora x86 so far).
> :)
> P
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20130212/d00ca437/attachment-0003.htm>