<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general">
    <title>gmane.comp.web.server.yaws.general</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3587"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3586"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3585"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3584"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3583"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3582"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3581"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3580"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3579"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3578"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3577"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3576"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3575"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3574"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3570"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3569"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3568"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3567"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3566"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3565"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3587">
    <title>omit yaws extension</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3587</link>
    <description>&lt;pre&gt; Hi,

yes, i thought about second solution. 
it seems to me that global appmod for '/' and {redirect_local, ...} is the same as arg_rewrite_mod. need to investigate all cons &amp;amp; pros.
nevertheless thanks for help.

~
Alex


On 24/05/2013 08:35, systemio systemio wrote:

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
&lt;/pre&gt;</description>
    <dc:creator>systemio systemio</dc:creator>
    <dc:date>2013-05-24T09:37:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3586">
    <title>Re: omit yaws extension</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3586</link>
    <description>&lt;pre&gt;
Hi,

I see 2 solutions to do what you want.

First, you can use an appmod bound on '/list' path, and do a "reentrant
call" (like an internal redirect in yaws) by returning {page,
"/list.yaws?id=..."}. But, with this solution, you need one appmod for
each rewritable path, or a global appmod on '/' to handle all requests.

Or, you can use a rewrite module (see arg_rewrite_mod parameter in
yaws.conf). This solution is probably the best.

&lt;/pre&gt;</description>
    <dc:creator>Christopher Faulet</dc:creator>
    <dc:date>2013-05-24T08:37:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3585">
    <title>Re: omit yaws extension</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3585</link>
    <description>&lt;pre&gt;
This is indeed work for a small and simple appmod.

-klacke


------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Claes Wikstrom</dc:creator>
    <dc:date>2013-05-24T06:57:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3584">
    <title>omit yaws extension</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3584</link>
    <description>&lt;pre&gt;
sorry if my question is incorrect.
i would like to reach something like MVC routing.
f.e. if i get www.site.com/list/all i will redirect to  www.site.com/list.yaws?id=all
f.e. if i get www.site.com/list/45689654 i will redirect to www.site.com/list.yaws?id=45689654
probably it is made by appmods, if it is i will dig dipper thru this way.

~
Alex


On 5/23/13 4:52 PM, systemio systemio wrote:

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
&lt;/pre&gt;</description>
    <dc:creator>systemio systemio</dc:creator>
    <dc:date>2013-05-24T06:35:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3583">
    <title>Re: omit yaws extension</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3583</link>
    <description>&lt;pre&gt;
Hi,

I'm not sure I understand the question, so there is a
default page at www.site.com/page called either of
www.site.com/page/index.{yaws,html,cgi} that directs to .. what

/klacke


------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Claes Wikstrom</dc:creator>
    <dc:date>2013-05-23T17:37:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3582">
    <title>omit yaws extension</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3582</link>
    <description>&lt;pre&gt;
Hi guys,

what is the true way to omit .yaws extension?
f.e. www.site.com/page redirects to www.site.com/page.yaws
sorry if the similar topic already exists

&lt;/pre&gt;</description>
    <dc:creator>systemio systemio</dc:creator>
    <dc:date>2013-05-23T14:52:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3581">
    <title>Re: yaws_pam.erl in yaws-1.96</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3581</link>
    <description>&lt;pre&gt;
Thanks, this was indeed not correct.


diff --git a/src/yaws_pam.erl b/src/yaws_pam.erl
index 1737e49..7927dc1 100644
--- a/src/yaws_pam.erl
+++ b/src/yaws_pam.erl
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -52,7 +52,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; start_link(Service, UseAccounting, UseSess) -&amp;gt;
  auth(User, Password) -&amp;gt;
      case has_nul(User) or has_nul(Password) of
          false -&amp;gt;
-            try  gen_server:call(pam_server, {auth, User, Password}, 10000) of
+            try  gen_server:call(?MODULE, {auth, User, Password}, 15000) of
                   Ret -&amp;gt;
                      Ret
              catch _:_ -&amp;gt;



Fixed

/klacke

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Claes Wikstrom</dc:creator>
    <dc:date>2013-05-21T10:25:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3580">
    <title>yaws_pam.erl in yaws-1.96</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3580</link>
    <description>&lt;pre&gt;
Hi,

A simple web application using Yaws in daemon mode with authentication
via PAM stopped working after upgrading from 1.94 to 1.96 : 
browser's login page keeps looping although correct login.  

Comparing Yaws sources revealed that yaws_pam.erl had one change made 
between those releases.  A simple test using yaws_pam.beam from 
release 1.94 with everything else from 1.96 verified the location 
of the problem - everything worked as usual with old yaws_pam. 

Committer: Claes Wikstrom &amp;lt;klacke-1h1PQOdKrizYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;  2012-11-09 13:06:48
SHA1 ID: 05be6e63a342fbfbcc8a5e9b92453b5d631df872
"handle case with DOS attack towards pam login with embedded NUL chars
in username or password. The protocol cannot handle NUL chars and Yaws
dies" 

.....
 auth(User, Password) -&amp;gt;
-    gen_server:call(?MODULE, {auth, User, Password}, infinity).
+    case has_nul(User) or has_nul(Password) of
+        false -&amp;gt;
+            try  gen_server:call(pam_server, {auth, User, Password}, 10000) of
+                &lt;/pre&gt;</description>
    <dc:creator>Jari Hellman</dc:creator>
    <dc:date>2013-05-21T08:55:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3579">
    <title>Re: Encoding comments for Erlang/master</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3579</link>
    <description>&lt;pre&gt;

Hi Nico, thanks, these changes are now on master,

--steve
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
&lt;/pre&gt;</description>
    <dc:creator>Steve Vinoski</dc:creator>
    <dc:date>2013-05-11T03:10:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3578">
    <title>Encoding comments for Erlang/master</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3578</link>
    <description>&lt;pre&gt;Some of the modules contain non-UTF8 characters and therefore need the
Latin-1 encoding comment in order to compile with Erlang/master
(or need to be converted to UTF-8)

The following adds the correct encoding headers to the affected files:

for file in yaws_xmlrpc.erl yaws_rpc.erl yaws_ls.erl yaws_jsonrpc.erl yaws_exhtml.erl ; do \
  sed -i -e "1i %% -*- coding: Latin-1 -*-" src/$file ; \
done


Nico

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Nico Kruber</dc:creator>
    <dc:date>2013-05-11T00:36:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3577">
    <title>Re: Soap server not concurrent</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3577</link>
    <description>&lt;pre&gt;Hi Andreas,

You can send me the diffs, I'll take a look at them.

--steve


On Fri, May 3, 2013 at 4:15 AM, AndreasH71 &amp;lt;
andreas.hellstrom-GcRVUZ4ttSYbhb6IIWwbbQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
&lt;/pre&gt;</description>
    <dc:creator>Steve Vinoski</dc:creator>
    <dc:date>2013-05-03T12:43:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3576">
    <title>Re: Soap server not concurrent</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3576</link>
    <description>&lt;pre&gt;
Hi Klacke!

This old issue was forgotten five years ago, but better late than never. We
have been running an old version of Yaws (1.72) since 2008, with some custom
made changes to make the soap server concurrent. A month ago we switched to
1.96 and implemented the changes in that code too.

What is the process of adding changes to Yaws? I'm not that familiar with
doing a 'proper patch', and would prefer to send the modified modules to
someone in the know.

In summary, the changes are:

- 3 files for the concurrent soap server (yaws_soap_srv + 2 new files)
- 3 files for adding a soap_workers gconf param.
- 1 file for a bug fix in yaws_stats.

Also, we've had an issue where we had to to encode soap data with utf-8
encoding, but I'm not sure how well that change will fit into Yaws?

How do I proceed with this?

Andreas



Claes Wikstrom wrote:

&lt;/pre&gt;</description>
    <dc:creator>AndreasH71</dc:creator>
    <dc:date>2013-05-03T08:16:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3575">
    <title>Re: Soap server not concurrent</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3575</link>
    <description>&lt;pre&gt;
Hi Klacke!

This old issue was forgotten five years ago, but better late than never. We
have been running an old version of Yaws (1.72) since 2008, with some custom
made changes to make the soap server concurrent. A month ago we switched to
1.96 and implemented the changes in that code too.

What is the process of adding changes to Yaws? I'm not that familiar with
doing a 'proper patch', and would prefer to send the modified modules to
someone in the know.

In summary, the changes are:

- 3 files for the concurrent soap server (yaws_soap_srv + 2 new files)
- 3 files for adding a soap_workers gconf param.
- 1 file for a bug fix in yaws_stats.

Also, we've had an issue where we had to to encode soap data with utf-8
encoding, but I'm not sure how well that change will fit into Yaws?

How do I proceed with this?

Andreas



Claes Wikstrom wrote:

&lt;/pre&gt;</description>
    <dc:creator>AndreasH71</dc:creator>
    <dc:date>2013-05-03T08:15:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3574">
    <title>Re: [erlang-questions] eheap_alloc: Cannot allocate 1272748 bytes of memory (of type "heap").</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3574</link>
    <description>&lt;pre&gt;


 --Chris H
 -- 
&lt;/pre&gt;</description>
    <dc:creator>chris hall</dc:creator>
    <dc:date>2013-04-14T05:34:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3570">
    <title>Re: Performance testing with OpenSTA</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3570</link>
    <description>&lt;pre&gt;

This is a likely culprit,

In general, performance tuning a complex concurrent erlang application
is non trivial, there are no magic tools.

Steves suggestion on tracing is a good starting point though.

/klacke

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Claes Wikstrom</dc:creator>
    <dc:date>2013-04-07T08:57:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3569">
    <title>Re: Performance testing with OpenSTA</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3569</link>
    <description>&lt;pre&gt;

Just to clarify this a bit: the purpose of hitting the system with just a
single request is to see how long the yaws_server:aloop function takes
under a no-load scenario. If you issue just one client request, the dbg
setup I described will detail two aloop calls, each providing a timestamp.
Just subtract the timestamps to get a timing for the aloop function.

BTW you're not somehow serializing your requests, are you? This could
definitely cause scalability issues as well as head-of-line blocking for
requests. Read one of my "Functional Web" columns for more details:

http://steve.vinoski.net/pdf/IC-Erlang_Web_Process_Bottlenecks.pdf

--steve
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html____________________&lt;/pre&gt;</description>
    <dc:creator>Steve Vinoski</dc:creator>
    <dc:date>2013-04-06T13:39:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3568">
    <title>Re: Performance testing with OpenSTA</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3568</link>
    <description>&lt;pre&gt;

You might try tracing. Can you get an interactive Erlang shell into your
system? If so then issue the following commands:

dbg:tracer(), dbg:p(all, [call, timestamp]).
dbg:tpl(yaws_server, aloop, []).

Then hit the system with one client request. You should see some trace
details on your Erlang console, including timestamps for the call in
question. That function is recursive and it includes pretty much all of the
server processing per request, so it's a quick way to help narrow down
where the time is going.

To stop the tracing: dbg:stop_clear().

--steve
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5&lt;/pre&gt;</description>
    <dc:creator>Steve Vinoski</dc:creator>
    <dc:date>2013-04-05T06:30:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3567">
    <title>Performance testing with OpenSTA</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3567</link>
    <description>&lt;pre&gt;Our app is using embedded YAWS server. I played around to do performance
tests with OpenSTA. The setup is 30 virtual users, all pass through the
test at once. OpenSTA is on virtual (VMWare) Windows XP machine and the
Erlang app on a Windows 8 machine which has 4 cores and 8GB of RAM.

OpenSTA reports 5 seconds response time for 10-15 requests but our own
in-app performance measurement shows nothing even close - the longest
request takes 200 milliseconds and it measures the whole message handing by
calling now/0 at entrance and timer:now_diff/1 before returning.

I tried to profile YAWS with eprof. Firstly, I saw 97% of the time was
spent in yaws_logger module. I turned access_log to false and now all YAWS
modules spend 0% according to eprof. But there is no improvement in the
response time according to OpenSTA.

I know this question is too vague but still doesn't hurt to ask :)

Has anyone experienced something similar?

Thanks for taking time to look at this.

Martin
----------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Martin Dimitrov</dc:creator>
    <dc:date>2013-04-04T14:21:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3566">
    <title>Re: Call yaws_api:websocket_send/2 from within the worker</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3566</link>
    <description>&lt;pre&gt;Thank you. That is exactly what I needed.

On 4/1/2013 4:56 PM, Steve Vinoski wrote:


------------------------------------------------------------------------------
Own the Future-Intel&amp;amp;reg; Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
&lt;/pre&gt;</description>
    <dc:creator>Martin Dimitrov</dc:creator>
    <dc:date>2013-04-01T15:39:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3565">
    <title>Re: Yaws and WebSockets with auth not working</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3565</link>
    <description>&lt;pre&gt;

Hi Vincent,

Have you tried defining a suitable &amp;lt;auth&amp;gt;...&amp;lt;/auth&amp;gt; structure in your
config? See page 55 of http://yaws.hyber.org/yaws.pdf .

--steve
------------------------------------------------------------------------------
Own the Future-Intel&amp;amp;reg; Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
&lt;/pre&gt;</description>
    <dc:creator>Steve Vinoski</dc:creator>
    <dc:date>2013-04-01T14:31:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3564">
    <title>Re: Call yaws_api:websocket_send/2 from within theworker</title>
    <link>http://permalink.gmane.org/gmane.comp.web.server.yaws.general/3564</link>
    <description>&lt;pre&gt;

Rather than casting to the websocket gen_server process, you could just
send it a message, which would end up in the gen_server's handle_info
function. If your websocket callback module exports a handle_info/2 fun,
that message will be passed on to your callback module via that function
along with the worker state, and then the worker can decide whether or not
to send a message to the client.

See the handle_info/2 fun description here:

http://yaws.hyber.org/websockets.yaws

--steve
------------------------------------------------------------------------------
Own the Future-Intel&amp;amp;reg; Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d_______________________________________________
Erlyaws-list mailing list
Erlyaws-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lis&lt;/pre&gt;</description>
    <dc:creator>Steve Vinoski</dc:creator>
    <dc:date>2013-04-01T13:56:05</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.server.yaws.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.server.yaws.general</link>
  </textinput>
</rdf:RDF>
