Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #100117

Re: Understanding Python from a PHP coder's perspective

From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Subject Re: Understanding Python from a PHP coder's perspective
Date 2015-12-08 10:09 +1100
Message-ID <mailman.38.1449529801.12405.python-list@python.org> (permalink)
References <f39f97f5-d7a1-4d7c-a7ac-527c2ffff76b@googlegroups.com> <44d92f52-4f92-470d-a724-102a14d185de@googlegroups.com> <mailman.35.1449525620.12405.python-list@python.org> <3e30fc58-4460-40a6-a639-22cd4d406f0b@googlegroups.com>

Show all headers | View raw


On Tue, Dec 8, 2015 at 9:27 AM,  <villascape@gmail.com> wrote:
> In regards to Chris's statement: "It openly and honestly does NOT reset its state between page requests"
>
> With PHP, I have sessions to preserve state.  I have a feeling that this is significantly different.  Yes?  How?  Does this somehow relate to how websockets are implemented?

All three are very different.

1) Process state.

You start up a Python program, and it sits there waiting for a
request. You give it a request, and get back a response; it goes back
to waiting for a request. If you change a global variable, or maintain
persistent state, or anything, the next request will 'see' that
change. This is completely global.

2) Sessions, cookies, and related concepts.

A request comes in, and the response goes out "Hi! You're caller
number 52635686412, and your call is important to us". Another request
comes in from the same web browser, and the browser says "Hi! You said
I was caller number 52635686412". The server looks up its information
about that caller, which might be in a database, or on disk in the
/tmp directory, or stored in process state (see above), or anything at
all. This gives the appearance of per-client state, but it's all a
simulation.

3) Websockets.

A client makes a request saying "Hey, I want a websocket, please". The
server says "Sure", and then they start maintaining true state. The
socket would be broken if either the server or the client restarts
(unlike sessions, although normally they're set up so a client restart
will wipe the session). Websocket state is per-connection.

Does that answer your question? The one I was talking about there was
#1, process state.

ChrisA

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Understanding Python from a PHP coder's perspective villascape@gmail.com - 2015-12-07 13:07 -0800
  Re: Understanding Python from a PHP coder's perspective villascape@gmail.com - 2015-12-07 13:21 -0800
    Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 09:00 +1100
      Re: Understanding Python from a PHP coder's perspective villascape@gmail.com - 2015-12-07 14:27 -0800
        Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 10:09 +1100
          Re: Understanding Python from a PHP coder's perspective villascape@gmail.com - 2015-12-07 17:00 -0800
            Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 14:26 +1100
        Re: Understanding Python from a PHP coder's perspective Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-07 16:10 -0700
        Re: Understanding Python from a PHP coder's perspective Cameron Simpson <cs@zip.com.au> - 2015-12-08 10:07 +1100
        Re: Understanding Python from a PHP coder's perspective Tim Chase <python.list@tim.thechases.com> - 2015-12-07 21:11 -0600
        Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 14:47 +1100
  Re: Understanding Python from a PHP coder's perspective Cameron Simpson <cs@zip.com.au> - 2015-12-08 08:33 +1100
  Re: Understanding Python from a PHP coder's perspective Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-07 14:37 -0700
  Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 08:40 +1100
  Re: Understanding Python from a PHP coder's perspective Terry Reedy <tjreedy@udel.edu> - 2015-12-07 16:53 -0500
  Re: Understanding Python from a PHP coder's perspective Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-07 14:59 -0700
  Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 09:03 +1100
  Re: Understanding Python from a PHP coder's perspective Tim Chase <python.list@tim.thechases.com> - 2015-12-07 16:28 -0600
  Re: Understanding Python from a PHP coder's perspective villascape@gmail.com - 2015-12-07 20:11 -0800
  Re: Understanding Python from a PHP coder's perspective Peter Otten <__peter__@web.de> - 2015-12-08 10:24 +0100
  Re: Understanding Python from a PHP coder's perspective Chris Angelico <rosuav@gmail.com> - 2015-12-08 20:40 +1100

csiph-web