StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POYAWS Websocket Trouble
primarykey
Id
7862348
data
AcceptedAnswerId
7904351
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-22T20:23:25.620
FavoriteCount
0
LastActivityDate
2016-12-07T22:10:05.507
LastEditDate
2011-10-25T19:57:55.517
LastEditorUserId
190887
OwnerUserId
190887
ParentId
0
PostTypeId
1
Score
2
ViewCount
1009
LastEditorDisplayName
text
Body
I'm trying to get the <a href="http://yaws.hyber.org/websockets.yaws" rel="nofollow">YAWS websocket</a> example from <a href="http://yaws.hyber.org/websockets_example.yaws" rel="nofollow">here</a> running on my local. It's a basic ws-based echo server. I have <ul> <li>YAWS set up and running on <code>localhost:8080</code> (direct from the Debian repos; no conf changes except pointing it to a new root directory)</li> <li>the code listing from the bottom of <a href="http://yaws.hyber.org/websockets.yaws" rel="nofollow">this page</a> wrapped in <code><erl></code> tags saved as <code>websockets_example_endpoint.yaws</code> </li> <li><a href="http://yaws.hyber.org/websockets_example.yaws" rel="nofollow">this page</a> saved as <code>index.yaws</code> (I literally copy/pasted the view-source for it, saved it as that file and pointed the socket request at <code>localhost:8080</code> rather than <code>yaws.hyber.org</code>).</li> </ul> When I visit <code>localhost:8080/websockets_example_endpoint.yaws</code> in-browser, it displays the text "You're not a web sockets client! Go away!", as expected. When I visit <code>localhost:8080</code>, it points me to the javascript enabled form, but the "Connect" button does nothing when clicked. If I leave <code>index.yaws</code> pointed at <code>yaws.hyber.org</code> instead of <code>localhost:8080</code>, the echo server connects and works exactly as expected. Can anyone give me a hint as to what I'm doing wrong (or alternatively, point me to source for a working example)?
Tags
<erlang><websocket><yaws>
Title
YAWS Websocket Trouble
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USInaimathi
UserOwnerUserId
1. USInaimathi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POYAWS Websocket Trouble
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POYAWS Websocket Trouble
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.