【AICon】AI 基础设施、LLM运维、大模型训练与推理,一场会议,全方位涵盖! >>> 了解详情
写点什么

REST changes in Rails Edge and RADAR

  • 2007-04-03
  • 本文字数:1034 字

    阅读完需:约 3 分钟

The development version of Ruby on Rails, Rails Edge, was updated with a change to the code that handles REST URLs. From the commit message for this change:"

Dropped the use of ; as a separator of non-crud actions on resources and went back to the vanilla slash. It was a neat idea, but lots of the non-crud actions turned out not to be RPC (as the ; was primarily intended to discourage), but legitimate sub-resources, like /parties/recent, which didn’t deserve the uglification of /parties;recent. Further more, the semicolon caused issues with caching and HTTP authentication in Safari. Just Not Worth It [DHH]"

Ryan Daigle gives a succinct overview of what this means:

Whenever you have a custom action route defined in Rails: map.resources :users, :collection => { :filter => :get } the resulting route no longer uses a semi-colon (;) to delimit the custom action: GET /users;filter and instead will use your standard forward-slash (/): GET /users/filter

Dave Thomas (PragDave) also reported these news and offered a thorough explanation of the reasons that made the semicolons seem necessary in the first place. After detailing that it’s only Web Browsers that require hacks like this, he ponders a solution for the problem:

Put the main application logic into a RESTful server. This is where all the CRUD-style access to resources takes place. Then, write a second proxy server. This is an HTTP filter, sitting between dumb browsers and your core resources. When browser-based users need to interact with your resources, they actually connect to this proxy. It then talks REST to your main server, and interprets the RESTful responses back into a form that’s useful on the browser. And this filter doesn’t have to be a dumb presentation layer - there’s nothing to say that it can’t handle additional functionality as well. Things like menus, user preferences, and so on could all sit here.

Since he likens Web Browsers to old 3270 terminals, also referred to as dumb clients, he names this idea “RADAR”: RESTful Application talking to Dumb-Ass Recipients.

2007-04-03 18:22580
用户头像

发布了 117 篇内容, 共 14.9 次阅读, 收获喜欢 0 次。

关注

评论

发布
暂无评论
发现更多内容

架构师训练营 - 第 3 课总结 -20200620- 软件设计

👑👑merlan

架构设计 软件设计 SOLID

SharePoint 往事之:一句话让 SharePoint 罢工

手艺人杨柳

SharePoint

加密与解密

返町

Cocoa 代码注释与文档生成

Edmond

ios CocoaPods 代码注释 Swift-Document iOS Document

Android APP启动白屏优化

小菜鸟学php

android白屏

必知必会,程序员都应该会的Linux的50个知识点!

Java小咖秀

Linux 面试 运维 Shell 经验

一种极致性能的缓冲队列

捉虫大师

Java 性能

架构师训练营第二周课后作业

赵凯

框架设计

如何写出高质量的代码?(浅谈代码规范、重构、单元测试的重要性)

Nick

单元测试 重构 代码重构 代码规范

互联网人的娱乐精神之28岁退休 & P8和生活助理的故事

码农神说

程序员 漫画 退休

新基建时代区块链应用场景进化

CECBC

新基建 区块链技术 去中心化 产业落地

当你输入get/set命令的时候,Redis做了什么

老胡爱分享

redis 源码分析

为什么Web开发人员在2020年不用最新的CSS功能

葡萄城技术团队

CSS

第二周学习总结

师哥

加入生财有术后,我获得了什么

Jay Wu

架构师训练营作业 (第三周)

王海

极客大学架构师训练营

英特尔宋继强:坚持科研的长期主义 推动AI向3.0时代跃迁

最新动态

数据库如何弹性伸缩?

Aaron_涛

数据库 架构 云原生

游戏夜读 | 中国的游戏制作人

game1night

面向对象设计课程小结

梅子黄时雨

极客大学架构师训练营

思想不进化的人都是可怜人

Neco.W

提升认知 思考 进步 进化

架构师训练营第三周

Melo

小师妹学JVM之:JIT中的LogCompilation

程序那些事

JVM 小师妹 性能调优 JIT 签约计划第二季

你真的了解敏捷吗?听马丁福勒聊敏捷

涛哥 数字产品和业务架构

敏捷 数字化转型

Flink on Zeppelin (5) 高级特性篇

章剑锋_Jeff

大数据 flink 流计算 Zeppelin

架构师训练营第三周-总结

无心水

极客大学架构师训练营

《零基础学 Java》 FAQ 之 17-怎么理解Java中的数组

臧萌

Java

跨云厂商部署 k3s 集群

米开朗基杨

k3s wireguard

UML实践-食堂就餐卡系统

shangyu

极客大学架构师训练营

请描述什么是依赖倒置原则,为什么有时候依赖倒置原则又被称为好莱坞原则?

一叶知秋

重学 Java 设计模式:实战责任链模式「模拟618电商大促期间,项目上线流程多级负责人审批场景」

小傅哥

设计模式 小傅哥 重构 代码优化 责任链模式

REST changes in Rails Edge and RADAR_Ruby_Werner Schuster_InfoQ精选文章