Session vs Context

@tykus In the permissions series on Laracast, Jeremy McPeak uses the context to store the permissions.

https://laracasts.com/series/mastering-permissions-in-laravel

I was rather used to use the session to do that (in an old application in vanilla PHP).

Is there any real best approach between Session and Context to store permissions ?

@vincent15000 Authentication uses session, permissions are normally looked up or sometimes cached. I suggest keep using these things as always. But just my opinion.

I prefer to lookup each time whether a user can or cannot do something.

@jlrdw For example I think that the Spatie package for permissions uses the cache.

@John Subut Thank you ... hmmm ... I can't imagine any situation where I could use a context, even after reading and re-reading the Laravel documentation.

Can you give some concrete examples please ?

@vincent15000, you're welcome!

Certainly!

use Illuminate\Support\Facades\Context;

// Set the user's preferred language
Context::put('user_language', 'en');

// Retrieve the user's preferred language in a subsequent request
$language = Context::get('user_language');

Dispatching the Job:

use App\Jobs\ProcessOrderJob;
use Illuminate\Support\Facades\Context;

// Set a context value
Context::set('userId', 123);

// Dispatch the job
ProcessOrderJob::dispatch(456);

Job Class:

namespace App\Jobs;

use Illuminate\Support\Facades\Context;

class ProcessOrderJob implements ShouldQueue
{
    public function __construct(public $orderId) {}

    public function handle()
    {
        // Retrieve the userId from the context (set earlier)
        $userId = Context::get('userId');
        logger("Processing order {$this->orderId} for user {$userId}");
        
        // Process the order
        // ...
    }
}