Client Server Application.

[cjinsocal581]

I have a server application. It gets information from a database every 2 minutes. And I have a client application that 2 users will be using. Both of these apps are VB.NET apps.

the information it gets needs to be sent to 2 people.

Here is what is currently in place. the server application (VB.NET App) is already built. It reads information from a database.
The client application is built but not working yet. (VB.NET)

I need the server app to send the data it reads (Basically a one line text string and a number) to the Client application over the network (LAN).

How can I accomplish this? I have been messing with Sockets but that sample app sends the information to ALL clients. I CANNOT have this happen. It is important to send the data based on the number. This number will be 1 or 2. If it is 1, then send the data to client A. If the number is 2, then send the data to client B.

the client application is made up of 2 text boxes. The first one will contain the number pulled from the database (1 or 2) and the second will contain the text string. (Client A will always have the number 1 in the first text box and Client B will always have the number 2 in the first text box)

Any ideas to make this work?

Please ask me any questions if any of this does not make sense.

 

[bboffin]

It sounds like what you need is to use Named Pipes which closely match your requirements. Unfortunately there are no classes provided within the standard .NET framework but a search for '.NET named pipes' on the internet will lead you to several example solutions of which the most useful appears to be at:

http://ivanweb.com/articles/namedpipes/index.cfm

This will require a small amount of work to use it with VB.NET - there are some notes about this in the Discussion section of the web page

Alternatively there is an article on MSDN:

http://support.microsoft.com/default.aspx?scid=kb;en-us;871044#kb3

This is specifically aimed at VB.NET.



Bob Boffin

 

[donutman]

A simple but kludgey solution would be to have the server write to a directory containing two sub-folders one for Client A and the other for Client B with appropriate shared rights. Each client than occasionally checks for the existence of a file which either transfers the information via the file name itself or the contents of a fixed file name.
-Karl

[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]

 

[donutman]

Oh, I see your other post.
-Karl

[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]