In our current_datetime
view, the contents of the page-the current date/time-were dynamic, but the URL (/time/
) was static. In most dynamic web applications though, a URL contains parameters that influence the output of the page. For example, an online bookstore might give each book its own URL, like /books/243/
and /books/81196/
. Let's create a third view that displays the current date and time offset by a certain number of hours. The goal is to craft a site in such a way that the page /time/plus/1/
displays the date/time one hour into the future, the page /time/plus/2/
displays the date/time two hours into the future, the page /time/plus/3/
displays the date/time three hours into the future, and so on. A novice might think to code a separate view function for each hour offset, which might result in a URLconf like this:
urlpatterns = [ url(r'^time/$', current_datetime), url(r'^time/plus/1/$', one_hour_ahead), url(r'^time/plus/2...