Pro Django (PDF)

Name: Pro Django
Brand: Springer-Verlag GmbH
SKU: 29580347
Price: 40.69 EUR
Availability: OnlineOnly

(Sprache: Englisch)

Autor: Marty Alchin

Schreiben Sie einen Kommentar zu "Pro Django".

Merken

Mehr zum Inhalt Leseprobe Autorenporträt Video

sofort als Download lieferbar

Bestellnummer: 29580347

eBook (pdf) 40.69 €

Download bestellen

Verschenken

Lastschrift, Kreditkarte, Paypal, Rechnung
Kostenloser tolino webreader

Produktdetails

Produktbeschreibung
Leseprobe
Autorenporträt
eBook Hilfe
Biblio. Angaben / Produktdetails

Produktinformationen zu „Pro Django (PDF)“

Django is the leading Python web application development framework. Learn how to leverage the Django web framework to its full potential in this advanced tutorial and reference. Endorsed by Django, Pro Django more or less picks up where The Definitive Guide to Django left off and examines in greater detail the unusual and complex problems that Python web application developers can face and how to solve them.

Provides in-depth information about advanced tools and techniques available in every Django installation
Runs the gamut from the theory of Django's internal operations to actual code that solves real-world problems for high-volume environments
Goes above and beyond other books, leaving the basics behind
Shows how Django can do things even its core developers never dreamed possible

Lese-Probe zu „Pro Django (PDF)“

CHAPTER 4 URLs and Views (S. 91-92)

Much of this book is split into fairly self- contained chapters, but this one covers two seemingly unrelated concepts together, because each relies very much on the other. URLs are the primary entry points to your site, while views are the code that respond to incoming events. What goes on in a view is very open- ended. Aside from accepting a request and returning a response, theres no particular protocol that views should adhere to, and no rules about what they are or arent allowed to do.

The possibilities for views are too vast to consider describing in detail, and there arent any utilities designed explicitly for views to use while executing. Instead, its possible to hook into the process Django uses to map Web addresses to the views they should execute. This makes the link between URLs and views extremely important, and a thorough understanding of it can enable further advanced techniques. Also, in terms of how Django manages incoming requests, URL configurations exist solely to dispatch a request to a view that can handle it. Discussing URLs and URL configurations independently of views would be of little value.

URLs

Since all incoming requests to a Web server originate with the Web browser accessing a URL, a discussion of URLs is an important place to start. The process taken by the browser to transform a URL into a message to be sent to the Web server is beyond the scope of this chapter, but Chapter 7 provides more information.

One common point of confusion is whether a Web address should be called a Uniform Resource Identifier (URI) or a Uniform Resource Locator (URL). Many people use these two terms interchangeably, regardless of whether they know the difference. In a nutshell, a URI is a complete addressing mechanism that includes two pieces of information.

always followed by a single colon. -
ent for different schemes, so not all URI paths look alike.

... mehr

URLs, on the other hand, are addresses from a small set of connection schemes whose path portions all conform to a single format. Included in this set are such common protocols as HTTP, HTTPS and FTPessentially the common protocols found on the Web today.

The path format shared by these protocols is as follows: used to access the resource, such as for standard HTTP. This is a slight extension to the scheme portion of the URI because it is assumed that all URL protocols will include two forward slashes following the colon. the resource can be found, such as . server responds to. Each protocol has a default port that will be used if one isnt supplied. For standard HTTP, this is , while for encrypted HTTP using the Secure Sockets Layer (SSL), it will be resource on the server, such as . So while all URLs are certainly URIs, not all URIs are URLs. That subtle distinction can be confusing when working on the Web because either term can be used to describe the addresses found everywhere. Since Django is built for the Weband thus the addresses covered under URL schemesthe rest of this book will refer to these addresses as URLs, as the full range of URIs might not be suitable for Djangos dispatching mechanism.

... weniger

Autoren-Porträt von Marty Alchin

By day, Marty Alchin works as a senior software engineer at Heroku, and after that, he writes and codes for fun and community. His blog can be found at http://martyalchin.com/ and he has profiles on many other services under the name Gulopine. In particular, his code can be found on GitHub and his random thoughts are on Twitter. He also accepts tips for his open source work at https://gittip.com/gulopine.