Skip to main content

Don't Stop 'Til You Get

 Don't Stop 'Til You Get

Today, we're going to learn about an alternative way of getting data from forms to the webserver.


So far, we've used post, which (kinda) packages up all the data from the form and sends it to the server.


We can think of this as the form controlling when the data is sent.


With the get method, the request for the data comes from the webserver. It effectively says gimme that data to the form.


You've probably seen get in use before. If you've ever seen a URL with a ? after the website name, then a bunch of = and maybe & symbols, then that website is using get.


So What's The Difference?

I'm glad you asked!


With post, the data in the form can't be seen by your web browser. Once it's sent, it's gone. This means that you can't bookmark or share a URL based on post data because it will be different for each user. Ever tried to drop those SO subtle present hints by sharing a shopping cart link? Only to get a link that doesn't show any shopping cart? Yep, that's the problem with post. The link for you will be different than the one for other users.


Get data encodes the data in the URL so we can bookmark & share it and get the same results from the page.


πŸ‘‰ Let's add some code to our Flask boilerplate to show how this works.


from flask import Flask

app = Flask(__name__)

@app.route('/', methods=["GET"])

def index():

  return 'Hello from Flask'

app.run(host='0.0.0.0', port=81)

 

πŸ‘‰ View the page in your broswer and add a variable or two to the end of the URL like this: 



  



Personalization
If I set my flask code up so that my request.args is assigned to a variable get, then I can use some selection to do some cool personalization.

from flask import Flask, request
app = Flask(__name__)
@app.route('/', methods=["GET"])
def index():
  get = request.args
  if get["name"].lower() == "david":
    return "Hello baldie"
app.run(host='0.0.0.0', port=81)


Look at what this does in the browser:

Return 'no data'
πŸ‘‰ I also need a return "No data" line in case there is no data present.

The reason that return "No data" is not in an else is due to the way that return works.

When a subroutine encounters a return, it exits the sub. So if our name is 'david', then the sub will return 'hello baldie' and then exit. Instead of carrying on to the return "No data".

from flask import Flask, request
app = Flask(__name__)
@app.route('/', methods=["GET"])
def index():
  get = request.args
  if get["name"].lower() == "david":
    return "Hello baldie"
  return "No data"
app.run(host='0.0.0.0', port=81)






Comments

Popular posts from this blog

Web Scraping

 Web Scraping Some websites don't have lovely APIs for us to interface with. If we want data from these pages, we have to use a tecnique called scraping. This means downloading the whole webpage and poking at it until we can find the information we want. You're going to use scraping to get the top ten restaurants near you. Get started πŸ‘‰ Go to a website like Yelp and search for the top 10 reastaurants in your location. Copy the URL.   url = "https://www.yelp.co.uk/search?find_desc=Restaurants&find_loc=San+Francisco%2C+CA%2C+United+States"   Import libraries πŸ‘‰ Import your libraries. Beautiful soup is a specialist library for extracting the contents of HTML and helping us parse them. Run the Repl once your imports are sorted because we want the Beautiful Soup library to be installed (it'll run quicker this way). import requests from bs4 import BeautifulSoup url = "https://www.yelp.co.uk/search?find_desc=Restaurants&find_loc=San+Francisco%2C+CA%2C+Unite...

HTTP & Sessions

 HTTP & Sessions One of the main protocols (rules that govern how computers communicate) on the web is called HTTP. HTTP is what is known as a stateless protocol. This means that it doesn't 'remember' things. It's a bit like having a conversation with a goldfish. You can ask a question and get a reply, but when you ask a follow up question, the original has already been forgotten, as has who you are and what you were talking about. So if HTTP is stateless, how come my news site remembers to give me the weather for my home town, my preferred South American river based online store tells me when it's time to order more multivitamins, and I'm justifiably proud of my #100days success streak? The answer is......... Sessions Sessions are a way of storing files on your computer that allows a website to keep a record of previous 'conversations' and 'questions' you've asked. By using sessions, we can store this info about the user to access later....

Client/Server Logins

 Client/Server Logins Waaay back when we learned about repl.db, we mentioned the idea of a client/server model for storing data in one place and dishing it out to multiple users. This model is the way we overcome the issue with repl.db of each user getting their own copy of the database. Well, now we can use Flask as a webserver. We can build this client server model to persistently store data in the repl (the server) and have it be accessed by multiple users who access the website via the URL (the clients). Get Started Previously, we have built login systems using Flask & HTML. We're going to start with one of those systems and adapt it to use a dictionary instead. πŸ‘‰ First, let's remind ourselves of the way the system works. Here's the Flask code. Read the comments for explanations of what it does: from flask import Flask, request, redirect # imports request and redirect as well as flask app = Flask(__name__, static_url_path='/static') # path to the static fil...