Tell me how to properly organize a local torrent rocking with a web interview. The torrent client itself has already been written. It remains to fasten the web. Is it worth raising a spring for the sake of "such" business, or are there alternative ways? If you need to screw the spring, how suitable is the mvc architecture?

The torrent client receives the .torrent file (or the path to the file) and the path to save. With the ability to issue statistics. No security and multiuse.

  • one
    There are no answers ... Mark the reason as "not paying attention" - Flippy
  • @ SergeyGrushin um, and how is it done here? When editing, nothing like this is observed - JVic
  • one
    Well, it means late, it's me in general, for the future) - Flippy
  • @Nofate, yes, it seemed to me that the spring would be very elegant for these businesses, anyway, like BelAZ for transporting potatoes. So I wanted to hear the views of more experienced - JVic
  • Iron is the simplest you can imagine) orange pi with 1 gigabyte on board - JVic

1 answer 1

And what doubts arose? You basically need to do a CRUD to manage torrents. Any MVC will do here. But you can without it. Architecturally, you already have a separation on the UI and the rocking itself.

If you do not have specific requirements for hardware resources, you can do what you like.

Options:

  • if you want to make the client part as thin as possible - Spring Boot, Spring MVC, any template engine (JSP, Thymeleaf, Velocity).

  • if you want to try SPA, then some not too heavy server (Jetty, Undertow, Ratpack) and JAX-RS binding for REST (Jersey, RESTeasy), or even without it, and UI to sculpt on JS.

  • if you want a SPA without JavaScript, then you can try the GWT (Google Web Toolkit), but this is a road to nowhere.

  • if the hardware is still weak, and you want something with a minimal footprint, then it is better to give up Java altogether, and try Python or even Lua. Under them is also enough as a full-fledged MVC, as minimalistic micro-web-frameworks.