3 ms·

I don't understand why they didn't generate a bunch of static pages from the database and avoid a whole lot of stress?

• mrkeen 3y ago
  Faceting. > A user will land on the search page and have the ability to “drill down” and narrow the results based on those properties. To make things much harder, all of these properties would come with exact counts.
  • ryanjshaw 3y ago
    Have a look at the archived page: https://web.archive.org/web/20070519214259/http://nymag.com/fashion/fashionshows/2007/spring/main/newyork/womenrunway/yigalazrouel/ https://web.archive.org/web/20070519214259/http://nymag.com/... Click on "Types of Clothing" - unfortunately the link isn't archived but you can see the URL: http://nymag.com/search/fashion-search.cgi?nymbreadcrumb_push=Bag&other_params=&results_per_page=20&sort_params=&search_type=fashion&autonomy_fieldname=Items&autonomy_fieldvalue=Bag&filter_prettyname=Bag http://nymag.com/search/fashion-search.cgi?nymbreadcrumb_pus... Judging from the query params, it looks like you can only filter one item at a time - seems like static pages would work.
    • renegade-otter 3y ago
      No, you could have drilled into multiple facets. I don't think the Archive cached the deep-nested results to see that. So, you could go "Dolce & Gabbana -> Bag -> Red". Then you could remove the middle one, for example, and end up with "Dolce & Gabbana -> Red" This gives you unlimited permutations of results, so static pages were a no go.