Stomp::__destruct

stomp_close

(PECL stomp >= 0.1.0)

Stomp::__destruct -- stomp_close — Closes stomp connection

Descrizione

Stile orientato agli oggetti (destructor):

public Stomp::__destruct()

Stile procedurale:

stomp_close(resource $link): bool

Closes a previously opened connection.

Elenco dei parametri

link: Solo stile procedurale: l'identificatore di connessione stomp restituito da stomp_connect().

Valori restituiti

Restituisce true in caso di successo, false in caso di fallimento.

Esempi

See stomp_connect().

Found A Problem?

Learn How To Improve This Page • Submit a Pull Request • Report a Bug

＋add a note

User Contributed Notes 2 notes

down

szasz dot attila at microsec dot hu ¶

11 months ago

Be careful, the lib does not send a DISCONNECT frame on destruction. Therefore the sessions will outlive the instance, accumulating in Artemis servers!

down

vanja at removethis dizyart period com ¶

7 years ago

Isn't it a little odd to have connect/disconnect in the constructor/destructor methods? 
I have a case where the connection is presumably kept alive until the PHP process ends:

<?php
class MyStompWrapper {
    public function doSend()
    {
        $stomp = $this->connect(); // returns Stomp Object
        $stomp->send('/destination', 'message', []);
        $this->disconnect($stomp);
        // $stomp still exists in this scope, hence, the connection is alive
    }

    private function disconnect(\Stomp $stompObj)
    {
        // only unsets the local $stomp pointer, does not actually disconnect
        unset($stomp);
    }

    private function connect():\Stomp
    {
        // try-catch block omitted for example brevity
        return new Stomp('url', 'username', 'password');
    }
}
?>

This means that, in order to handle disconnecting, I have to create and destroy the Stomp object within the same scope.

＋add a note