How To: Windows Service w/ remote clients, i.e SQL Server 
Author Message
 How To: Windows Service w/ remote clients, i.e SQL Server

If you where to build a new solution using .Net, similar to Microsoft SQL
Server, where a service process runs on one server while either WinForm
clients or ASP clients run on another, using an object library to
programmatically get at that service, what project styles and imports would
you use?

Online documentation has most solutions leaning towards e-commerce and lack
the ability to provide a static windows service, providing a single
execution instance, whereas processing takes place in absence of a client,
i.e. a backup operation or I/O operations with hardware.

Secondly, what if the application required broadcasting of real-time data
and client polling for that data is not an option. It's one thing to expose
a library to execute remote procedures, but information is required at the
client side that is not the result of an operation performed by that client.
I.e. clients receiving a notification when a user on another machine
performs a task such as entering an order.



Mon, 18 Aug 2003 14:11:39 GMT  
 How To: Windows Service w/ remote clients, i.e SQL Server
Visual Studio.net has an NT service project type.

To deliver notifications use UDP

Phil


Quote:
> If you where to build a new solution using .Net, similar to Microsoft SQL
> Server, where a service process runs on one server while either WinForm
> clients or ASP clients run on another, using an object library to
> programmatically get at that service, what project styles and imports
would
> you use?

> Online documentation has most solutions leaning towards e-commerce and
lack
> the ability to provide a static windows service, providing a single
> execution instance, whereas processing takes place in absence of a client,
> i.e. a backup operation or I/O operations with hardware.

> Secondly, what if the application required broadcasting of real-time data
> and client polling for that data is not an option. It's one thing to
expose
> a library to execute remote procedures, but information is required at the
> client side that is not the result of an operation performed by that
client.
> I.e. clients receiving a notification when a user on another machine
> performs a task such as entering an order.



Mon, 18 Aug 2003 20:48:38 GMT  
 How To: Windows Service w/ remote clients, i.e SQL Server
Phil,

What about the client running in either a browser or Win32 app, that
interacts with the service? UDP may work for the broadcast but what if I
want to make property or method calls, much the same as you would with SQL
DMO? DCOM ( probably a dirty word in .Net ), Named Pipes ( named what? )?
What does .Net offer me that improves this type of architecture?

I've read .Net docs on Remoting, Sockets, and Web Services, all of which
lack comprehensive if any Visual Basic example code. My current release uses
sockets in VB6, but there's alot of data coersion to really get it to do the
trick. I would like to get rid of having to concern myself with things like
multiple messages in a single packet and the {*filter*} problem of never being
able to yield to the OS during the case where a socket receives more than
one message and does not complete before the next one comes in.

Thank you.


Quote:
> Visual Studio.net has an NT service project type.

> To deliver notifications use UDP

> Phil



> > If you where to build a new solution using .Net, similar to Microsoft
SQL
> > Server, where a service process runs on one server while either WinForm
> > clients or ASP clients run on another, using an object library to
> > programmatically get at that service, what project styles and imports
> would
> > you use?

> > Online documentation has most solutions leaning towards e-commerce and
> lack
> > the ability to provide a static windows service, providing a single
> > execution instance, whereas processing takes place in absence of a
client,
> > i.e. a backup operation or I/O operations with hardware.

> > Secondly, what if the application required broadcasting of real-time
data
> > and client polling for that data is not an option. It's one thing to
> expose
> > a library to execute remote procedures, but information is required at
the
> > client side that is not the result of an operation performed by that
> client.
> > I.e. clients receiving a notification when a user on another machine
> > performs a task such as entering an order.



Wed, 20 Aug 2003 11:20:32 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. Remote Automation : Windows 3.1 client/ Windows NT Server

2. checking windows service status on remote server

3. Getting Client Connected to remote SQL server

4. Windows Service and SQL Server

5. Client side ActiveX control accessing SQL Server with Windows NT Security

6. Import xls file into SQL Server using VBscript and exe function on remote server

7. Start Remote Windows NT Service

8. How to receive a remote computers Windows NT Services in VB 5.0

9. How to retrive object type from remote server by using remoting services

10. Trying to shut down Services on Remote Server on network

11. DCOM settings needed on client and server for remote Outlook application

12. .Net Client Error: Unable to connect to the remote server

 

 
Powered by phpBB® Forum Software