litesoft
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
Premise:
You have static or non-changing content, and
some relatively rapid changing content, and you
do NOT want your users to have to actively manage
their browser cache.
For static content, the web server (non-IIS) usually default to cache life is infinite (My friends have indicated that their development IIS defaults to "do not cache"). And the solution is to rename the content when it changes. The problem is that your users have to know what the "new" name is. The solution is to have a single page that is a forwarding/redirect page set to "do not cache" that forwards/redirects to your new named content.
This basic concept can be applied to a site versioning approach. The idea at a minimum (for the 1st version) is to create two web apps:
Version-less app: that forwards/redirects each page
that you want to allow deep linking on (this can
be a Servlet that forwards all requests), at a
minimum the starting page, to the current
Versioned app. All of these "pages" are set to
"do not cache".
Version_01 app: that is your actual Web app.
As "Version_01" (which I usually abbreviate as
"v01" is actually part of the URL, all references
within the app should be relative!
Deploying a new version involves three steps:
1) Actually deploying the new Version_nn web app and
testing it w/ direct versioned URLs.
2) Adjusting (and re-deploying) the Version-less
app to reference (forward/redirect to) the
new current versioned app.
3) Replacing the previous versioned web app with
either:
a copy of the Version-less app
or
a web app that forwards/redirects all
pages to the Version-less app.
|
Revision |
Author |
Commited |
Message |
63
|
GeorgeS
|
Tue 28 Sep, 2010 13:55:00 +0000 |
|