Correct way to create global resources

[Samuka007]

Use this form:

#[actix_web::main]
async fn main() -> std::io::Result<()> {
    let global_vec: Mutex<Vec<VirtualResource2>> = Mutex::new(Vec::new());
    let global_resources = web::Data::new(global_vec);

    HttpServer::new(move || {
        App::new()
            .app_data(global_resources.clone())
            .service(web::resource("/").route(web::get().to(index)))
    })
    .bind(("127.0.0.1", 8889))?
    .run()
    .await
}

Instead of this:

static VIRTUAL_RESOURCES: LazyLock<Arc<Mutex<Vec<VirtualResource>>>> = LazyLock::new(|| Arc::new(Mutex::new(Vec::new())));

#[actix_web::main]
async fn main() -> std::io::Result<()> {
    let server = HttpServer::new(move || {
        App::new()
            .service(web::resource("/").route(web::get().to(index)))
        })
        .bind(("127.0.0.1", 8889))?
        .run();

    let server_handle = server.handle();
    let server_task = rt::spawn(server);

    let shutdown = tokio::spawn(async move {
        tokio::signal::ctrl_c().await.unwrap();

        let server_stop = server_handle.stop(true);

        server_stop.await;

        // NOW you have to manuel drop it when signal arrive
        VIRTUAL_RESOURCES.lock().unwrap().clear();
    });

    let _ = tokio::try_join!(server_task, shutdown).expect("unable to join tasks");

    Ok(())
}

In the first case, the drop call can be called automatically. But in the second case, to correctly release the resources, things just get a lot more complicated due to the "easy" global variable.