title: PHP (Laravel) and queued events, at what point is the session no longer accessible?
body: <p>This question is more ignorance on my part about how sessions work behind the curtains...  But I'm working with Laravel 5, I have a very simple controller statement that sets a session variable when a user visits the site by clicking on a referral link.</p>
  
  <pre><code>public function checkReferralCode($code)
  {
      session(['referral_code'=&gt;$code]);
      ....
  </code></pre>
  
  <p>this session value is of course available throughout the project with</p>
  
  <pre><code>session('referral_code');
  </code></pre>
  
  <p>my question is, what happens if I call an event that is queued and later processed with say Beanstalkd? If that event needs a session variable, will that event lose track of what the session and session variables are?  In other words, should I make sure to pass those variables to the queued event to ensure access?</p>
  
  <p>Right now my events are simply synchronous, but I'd like to make sure if I ever need to implement beanstalkd, that I don't have any surprises.</p>