The term applied to the middle tier can be influenced by its role. Typically, it is a controller in an MVC paradigm, a business logic layer, a communication/transport layer or a combination of these.
Terms I've used:
Middle Tier (admittedly a generic cop-out -- could apply to your situation)
Business Logic Layer or Business Objects - not the best fit for your app...
Transport Layer -- seems more apt to your situation, though I'm not convinced "everybody will immediately know what you're talking about" when you introduce this term.
Controller (probably too abstract -- Model-View-Controller)
发布评论
评论（4）
我们最近创造了术语“中间层”
We've recently coined the term "Intermediary Layer"
适用于中间层的术语可能会受到其角色的影响。通常，它是 MVC 范例中的控制器、业务逻辑层、通信/传输层或这些层的组合。
我使用过的术语：
中间层（诚然是通用的逃避 - 可能适用于您的情况）
业务逻辑层或业务对象 - 不是最适合您的应用程序...
传输层 - 似乎更适合您的情况，尽管我不相信当你介绍这个术语时“每个人都会立即知道你在说什么”。
控制器（可能太抽象——模型-视图-控制器）
The term applied to the middle tier can be influenced by its role. Typically, it is a controller in an MVC paradigm, a business logic layer, a communication/transport layer or a combination of these.
Terms I've used:
Middle Tier (admittedly a generic cop-out -- could apply to your situation)
Business Logic Layer or Business Objects - not the best fit for your app...
Transport Layer -- seems more apt to your situation, though I'm not convinced "everybody will immediately know what you're talking about" when you introduce this term.
Controller (probably too abstract -- Model-View-Controller)
总是可以尝试使用“数据访问层”
Could always try going with "Data-Access Layer"
也许翻译层？
Maybe Translation layer?