If you have any sort of caching enabled then the uniqueid will not work properly e.g. unset( $_SESSION['pdf_uniqueid'] ) won't work as expected, because isset( $_SESSION['pdf_uniqueid'] ) will sometimes grab a cached version of the value.
Of course this can be fixed with changes to the server config or headers, but thats not preferable as it wont work for everybody. This is likely why WordPress has stopped using $_SESSION to store data, and utilises the database instead.
Do you have any plans of moving from $_SESSION to database storage to keep inline with current WordPress best practices?
If you have any sort of caching enabled then the uniqueid will not work properly e.g. unset( $_SESSION['pdf_uniqueid'] ) won't work as expected, because isset( $_SESSION['pdf_uniqueid'] ) will sometimes grab a cached version of the value.
Of course this can be fixed with changes to the server config or headers, but thats not preferable as it wont work for everybody. This is likely why WordPress has stopped using $_SESSION to store data, and utilises the database instead.
Do you have any plans of moving from $_SESSION to database storage to keep inline with current WordPress best practices?