MVC、服务层和文件上传/存储
我正在使用 Zend Framework 的分层架构。
我有 MVC：
控制器> (DTO)服务(Service Layer)> （DO）存储库>持久性
现在我必须处理图片库。 上传过程由前端处理，但是拇指的生成是由哪部分负责的呢？
我是否必须从前面将图片存储到临时文件夹，将临时路径传递给将处理调整大小并将文件移动到存储服务器文件夹的服务？
或者我是否必须从前面处理图片大小调整/存储过程并仅将图片 URL 传递给服务？
服务层的目的是移动应用程序逻辑并保持控制器的精简。但对于这些情况，我真的不知道谁负责什么:)
你有什么建议吗？
I'm a using a layered architecture with Zend Framework.
I have MVC with :
Controllers > (DTOs) Services (Service Layer) > (DOs) Repositories > Persistance
Now i have to handle image galleries.
The upload process is handle by the front, but what part is responsible for the thumbs generation ?
Do i have to store pictures to a temp folder from the front, passing the temp path to a service which will handle resizing and will move the file to the storage server folder ?
Or do i have to handle the pictures resizing/storage process from the front and pass only the picture URL to the service ?
The purpose of the Service Layer is to move application logic and keep the controllers thin. But for those cases i really don't know who is responsible of what :)
Have you any advices ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
“对于那些情况”是什么意思？如果你的策略是将所有逻辑放在服务层中，那么我找不到你应该犹豫的理由......
生成拇指绝不是一个“特殊”过程，所以它应该在专门的服务中，照常。
关于前层如何将图像存储为临时文件的附带细节不应改变这一点。
前端知道如何上传数据，就可以了；然后，图像处理服务可能会起带头作用并生成所需的任何拇指。
哈
What do you mean by "for those cases" ? If your strategy is to put all logic in the service layer, then I can't find a reason why you should hesitate...
To generate thumbs is by no mean a "special" process, so it should be in a dedicated service, as usual.
The incidental detail about how images are stored as temp files by the front layer should not change that.
The front knows how to upload data, that's fine and that's it; the image-processing services may then take the lead and generate whatever thumbs are needed.
hth