Sharing complex objects across controller methods Laravel 5.1

Question

Given the following scenario:

controller@method_a spawns a process (Symfony Process object) asynchronously, controller@method_b needs to interact with the process

How would you implement sharing the Process object?

Things I've went over:

controller properties don't persist, as with each request the controller gets reinstantiated
Session can't store complex objects, and serialization would take the soul of it
database can't store complex objects either

edit:

To the serialization issue:

    $process = new Process("dir");
    $process->start();
    $x = serialize($process);
    dd($x);

If I remove the $process->start(), it does not fire Serialization of 'Closure' is not allowed. But I can't do anything with a handle for a process that's not started.

If this is one controller, you can use public $var to hold data and share with another method. — Piotr Kazuś, Nov 10 '16 at 12:47

score 0 · Answer 1 · answered Nov 10 '16 at 12:42

0

I guess the only option here is to serialize an object and persist it somewhere (DB, session, file). In next request, pull it and unserialize.

answered Nov 10 '16 at 12:42

Alexey Mezenin

158,981
26
290
279

That fires a `Serialization of 'Closure' is not allowed` exception. – Rápli András Nov 10 '16 at 13:01
Thanks. Check this asnwer http://stackoverflow.com/a/13734344/1227923 maybe it will give you some idea. – Alexey Mezenin Nov 10 '16 at 13:53

Sharing complex objects across controller methods Laravel 5.1

1 Answers1