Can someone point me in the right direction on how to do the following?
I need to create a small desktop application that uses FileSystemWatcher to look for file creation. When a file has been detected, it uploads the file to a server (Web API). So far so good.
Here comes the problem: The file(s) need to attach themselves to the 'page' the current user is on.
A user creates a 'New Page' on our website, fills in some information and then imports files that our FileSystemWatcher detects. Somehow the Web API need to find what session the user is on and attach the files to this session and then display the files/images on the current 'page'.
My idea is to add another cell to the user table in the database called "CurrentSession", that holds a uniqueidentifier (pointing towards the PageId). But this Id needs to be cleared if the user leaves the page, closes the browser, disconnects, log-out and so on. It's vital that the files do not attach themselves to the wrong page.
Am I over thinking this? Or is there a better way to achieve this?
I need to create a small desktop application that uses FileSystemWatcher to look for file creation. When a file has been detected, it uploads the file to a server (Web API). So far so good.
Here comes the problem: The file(s) need to attach themselves to the 'page' the current user is on.
A user creates a 'New Page' on our website, fills in some information and then imports files that our FileSystemWatcher detects. Somehow the Web API need to find what session the user is on and attach the files to this session and then display the files/images on the current 'page'.
My idea is to add another cell to the user table in the database called "CurrentSession", that holds a uniqueidentifier (pointing towards the PageId). But this Id needs to be cleared if the user leaves the page, closes the browser, disconnects, log-out and so on. It's vital that the files do not attach themselves to the wrong page.
Am I over thinking this? Or is there a better way to achieve this?