durusmail: quixote-users: Re: New Quixote site, and expire problem
New Quixote site, and expire problem
2005-09-11
2005-09-11
2005-09-11
2005-09-11
2005-09-11
2005-09-11
Re: New Quixote site, and expire problem
Re: New Quixote site, and expire problem
2005-09-13
2005-09-13
2005-09-13
2005-09-14
Re: New Quixote site, and expire problem
Mike Orr
2005-09-13
On 9/13/05, Neil Schemenauer  wrote:
> Something is adding a second Expires header (maybe Apache) and
> giving the expire time as 1 minute.

It may be in the Mac's standard httpd.conf somewhere.  We're trying to
play nicely with the Mac's configuration dialog, which isn't always
possible.  We'll probably use a second Apache instance for the Quixote
sites and keep the configurator away from it.

> Why doesn't /1/search_entries_action?category=X just return the page
> rather than redirecting back to /1/entries and then having
> /1/entries return the page?  If you did do that then you could
> probably allow the browser to cache the
> /1/search_entries_action?category=X pages for some period of time.

To separate searching from paging.  To avoid having one method display
the first page and the other method display all the other pages.  To
avoid making the child pages having to know the criteria  to link back
to the results page.  To have one pattern we could use for all search
pages.

> Allowing caching via "Expires" is a huge performance boost because
> if the page is not yet expired then browser does not have to contact
> the server at all (unlike, for example, Last-Modified +
> If-Modified-Since).  For users not at your site, the latency of a
> HTTP request/response cycle is probably very noticeable.

Yes, I'll activate it for the images.  I'm not sure it's appropriate
for a results page though.

> > I'm going to rearrange the URLs as David suggested ( /1/categories/4 )
> > and do the query for every page.
>
> Just to be clear, you don't have to differentiate the URIs by path
> (although it's often a nice design).  Using a query string is also
> sufficient.  The root problem is that /1/entries is overloaded.  If
> you want a quick hack, have /1/search_entries_action?category=X
> redirect to /1/entries?category=X.  You would have to add a hidden
> field to the paging form but that shouldn't be hard.  With that
> change, clicking on 'Next' would go to /1/entries?category=X&page=1.
>
> Hope that helps,

Thanks for your suggestions, especially Ethereal.

--
Mike Orr  or 
reply