Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have written a C# server which listens for Tcp connections. A client can connect to the server and send data, mostly filenames. The data that the server receives needs to be shown on a website written in ASP.NET.
I was thinking of using pipes to send the data from the server process to the website. Is this the right way to do it or are there other (smarter) ways of doing this?
I don’t think pipe are an option since the process hosting the website ( the worker process ) can be recycled at any moment and you dont have control on this. Is better to have a plain old database to share information between your service and the asp.net app. If you think the db is too much, you can use a plain file ( or an xml does not matter ) but in this case you have to keep an eye to the concurrency since both process can concurrently try to open the file.