上一篇博客我们讲到了页面缓存,这次楼主讲的URL缓存其实和页面缓存是一个道理,但就是改了一点点细节,我们以一个
差不多的例子来讲解一下URL缓存(基本思路和页面缓存一样):
1.首先来看看没有改过的代码:
@RequestMapping("/goods/to_detail/{goodsId}")
public String detail(Model model, MiaoshaUser user,@PathVariable("goodsId") long goodsId) {
model.addAttribute("user", user);
GoodsVo goods = goodsService.getGoodsVoByGoodsId(goodsId);
model.addAttribute("goods", goods);
long startAt = goods.getStartDate().getTime();
long endAt = goods.getEndDate().getTime();
long now = System.currentTimeMillis();
int miaoshaStatus = 0;
int remainSeconds = 0;
if (now < startAt) {// 秒杀还没开始,倒计时
miaoshaStatus = 0;
remainSeconds = (int) ((startAt - now) / 1000);
} else if (now > endAt) {// 秒杀已经结束
miaoshaStatus = 2;
remainSeconds = -1;
} else {// 秒杀进行中
miaoshaStatus = 1;
remainSeconds = 0;
}
model.addAttribute("miaoshaStatus", miaoshaStatus);
model.addAttribute("remainSeconds", remainSeconds);
return "goods_detail"
}
和上一篇博客差不的代码,只是实现的功能是通过不同的id来查询不同的详情商品页面
2.我们把上面的代码通过URL缓存来改一改:
@RequestMapping("/goods/to_detail/{goodsId}")
@ResponseBody
public String detail(Model model, MiaoshaUser user, HttpServletRequest request, HttpServletResponse response,@PathVariable("goodsId") long goodsId) {
model.addAttribute("user", user);
GoodsVo goods = goodsService.getGoodsVoByGoodsId(goodsId);
model.addAttribute("goods", goods);
long startAt = goods.getStartDate().getTime();
long endAt = goods.getEndDate().getTime();
long now = System.currentTimeMillis();
int miaoshaStatus = 0;
int remainSeconds = 0;
if (now < startAt) {// 秒杀还没开始,倒计时
miaoshaStatus = 0;
remainSeconds = (int) ((startAt - now) / 1000);
} else if (now > endAt) {// 秒杀已经结束
miaoshaStatus = 2;
remainSeconds = -1;
} else {// 秒杀进行中
miaoshaStatus = 1;
remainSeconds = 0;
}
model.addAttribute("miaoshaStatus", miaoshaStatus);
model.addAttribute("remainSeconds", remainSeconds);
// URL缓存:1.查询redis (和页面缓存唯一不同的一点就是多了goodsId,因为每个商品的详情都不通,所以要区分开来)
String html = redisService.get(GoodsKey.getGoodsDetail, ""+goodsId, String.class);
if (!StringUtils.isEmpty(html)) {
return html;
}
// 假如redis查询不到数据,则:熏染html(通过SpringBoot的themleafViewResovler接口的实现类SpringWebContext来操作)
SpringWebContext ctx = new SpringWebContext(request, response, request.getServletContext(), request.getLocale(),
model.asMap(), applicationContext);
// 手动进行渲染:thymeleafViewResolver
html = thymeleafViewResolver.getTemplateEngine().process("goods_detail", ctx);
// 2.将手动渲染完毕的html存放到redis中
if (!StringUtils.isEmpty(html)) {
redisService.set(GoodsKey.getGoodsDetail, ""+goodsId, html);
}
return html;
}
和上次页面缓存不同的一点是:
这次的redis的key多了一个goodsId,这个goodsId也在URL上,通过goodsId来查询每个商品对应的详情页面,
大部分和页面缓存一样,就是goodsId作为key的同时也是URL的一部分,所以可以叫做URL缓存!