Note, WSGI is not a piece of software -- it is just a specification for how the web server and the web app communicate with each other.
Anthony On Sunday, May 4, 2014 5:01:21 PM UTC-4, Jesse Ferguson wrote: > Thank you Ricardo, I watched videos and read into the docs of everything > you listed, Only thing I am bit unclear on is "WSGI", If Im understanding > correctly its really just a Middleware that sits between a Sever and a > python Framework. However Im a bit confused How the stack works when > implementing Gevent-socketio, > > What i think is going on... > > WSGI Handles talking to the Framework (in our case web2py) and the server, > (in essence a server to the server bridging the gap) > > Gevent-socket.io Handles socket connections coming from socket.io on the > browser > > SocketIOServer Handles talking to WSGI and to the Browser Viewing the html > > So would the stack be like this? > > From a Browsers connection down > > > SocketIOserver ^^^ > Gevent-socket-io ^^^ > WSGI ^^ -> #WSGI sits between server and framework > Web2Py Framework ^^^ > > > I would like to start building a site with web2py and socket.io that will > display a lot of live data and have a chatbox, would you suggest I build > the stack in a vm and work from there using Nginx? Or is the SocketIOserver > sufficient for Development? > > Or am I way off and need to go back to the docs? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
