A Web Service is not really a good candidate for a chat server. It's possiblt, but you'll have to rewrite large portions of your server and client apps.
If your server is already written properly, you should be able to put it on any machine and run it without modification. All you need to do is supply the client app with the IP of the server running the server app.
I built client server application which using tcp protocol
example code :
listener = New Sockets.TcpListener(System.Net.IPAddress.Any, PORT_NUM)
If im the server and I behind router, i cannot communicate with a client side only if i open a port in my router.
I wonder how all multiplayer's games work if no one needs to open any port?
Can it be the server side is a not at home computer but a real server that control many clients?
Should i need to run a thread in the server that manage all players (all players are the clients?) ?
if this the way (using a thread that always run in the server and manage all players from home computers which are the clients)
What will happened if the thread stuck or the server shutdown, this will kill all users(players).
Ill appreciate any help building multiplayer's gaming manage by server side (or any other good technology for multiplayer's)
If a machine has multiple versions of .NET Framework installed say 1.1 and 2.0. Further still if there are .NET assemblies that are built on both flavours. And if we have a mix of ASP.NET pages that are written in 1.1 and 2.0. I presume that all pages are hosted as one application.
1)where would you ideally place the version specific assemblies.
2) Which version of the web.config would you deploy on the web root, since i understand they are different between 1.1 and 2.0 ?
3) Is it a fair statement that if there are some ASP.NET 2.0 specific pages then deploy them in a different folder that has 2.0 specific web.config ?
4) Would there be issues if we host this on IIS 6.0 since the same application pool cannot process multiple .NET Versioned components. Refer http://dotnetmystery.blogspot.com
And if we have a mix of ASP.NET pages that are written in 1.1 and 2.0. I presume that all pages are hosted as one application.
It was looking good up to here.
Only one version of ASP.NET can be registered with IIS. There is *no* way you can say that different pages within the one site are different versions, and apart from that, you can only run one version on a web server at a time.
What you want, can't be done at all.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
My idea was to have a mix of ASP.NET pages that are written in 1.1 and 2.0, and have that hosted as one single Web application. Currently our application has a mix of ASP, ASP.NET 1.1, but since we are integrating a new application into the current one, we want the new code to be written in ASP.NET 2.0 and migrate all the existing ASP and ASP.NET 1.1 to ASP.NET 2.0 pages at a later point of time. Since all this is one appln, we would like to have this run as one appln.
But reflecting on your thoughts, i guess you are right , that we cant be doing this, since IIS routes different ASP.NET versions to different ASP.NET Worker processes, rather they are defined so in IIS metabase, so they would never execute as one application.
I'm sorry, Christian, but you're wrong: different 'web applications' can be run with different .NET versions. However, all web applications sharing a worker process (pool) must have the same .NET version.
A 'web application' differs from a virtual directory, and has a different icon (IIS 5.x uses an open box icon rather than a folder icon; IIS 6.0 uses a 'gear' icon rather than a folder). To convert a folder into a web application, click Create under 'Application Settings' in the folder's properties in the IIS management console.
In IIS 5.x (Windows 2000 and XP), this is automatic - the appropriate version of the ISAPI Filter is loaded depending on what the metabase has configured, which then loads the appropriate worker (aspnet_wp.exe) process. ASP.NET 2.0 adds a new ASP.NET page to the application's property sheet which permits the version to be selected. If this page isn't present, ASP.NET 2.0 is probably not installed correctly. To install it, but keep any existing web applications using ASP.NET 1.1, run aspnet_regiis -ir.
The IIS 5.x process model supports in-process, shared process or dedicated process hosting. All applications set to 'shared process' use the same dllhost.exe worker process. However, ASP.NET always creates its own worker processes - your code does not run in dllhost.exe.
In IIS 6.0, the worker process (w3wp.exe) has native support for ASP.NET hosting. Web applications can run in different 'application pools'. An application pool uses at least one process, and potentially more than one, to run the set of applications in the pool. However, the ASP.NET version required for each application is not checked. Only one version of the .NET CLR can be loaded into a process. If you configure an application pool with a set of applications that require different versions, you will have problems as the first application to load into a worker process dictates which version of the CLR is loaded. It's best to keep your .NET 2.0 applications in a separate pool from your .NET 1.1 applications to avoid problems with CLR version mismatches.
A web application can only use one version of the Framework. You would have to place the pages developed for the other version into a different folder (this could be a subfolder) and create a new Application (click Create under Application Settings in the folder's properties in the IIS management console).
You should place the appropriate version of web.config under the root that matches the version of ASP.NET you have selected for the root. The application you create for the other version should have its own web.config: settings are not inherited from the root configuration.
If running on IIS 6.0, you should place your ASP.NET 1.1 applications in a different application pool to the ASP.NET 2.0 applications to ensure that they get separate worker processes.
I don't know... Let me see... Hamster Dance song plays... ... well what do you know - It works!! Of course, it gives you the "Did you mean: ruby on rails tutorials" correction, but hey, results abound!