T
Tom Leylan
I'd like to find/have a discussion about the various ways an application
server could be implemented. So the upsides and downsides can be discussed.
In case I'm using the term wrong by "app server" I mean a centralized
"business information service" that could be readily accessed by client
software. Initially this would be on a LAN but (like everything) the
requirements would likely grow to permitting general Internet access.
It shouldn't require .Net to exist on the client and ideally it shouldn't
even require .Net to exist on the server. I'd like to use .Net to write it
but it doesn't "have to" hook into everything that .Net offers. I'd just
like the ability to accept requests for information and send it back.
(Don't know if I should go on until I get a response... but I probably
haven't provided enough information yet... so)
Generally speaking the server would return data fetched from a database but
of course where the information came from shouldn't be important to the
client requesting it. So let me provide a few simples examples. Naming the
server "myserver" it should be possible to request the following (but not
necessarily using this syntax):
myserver.WhatTimeIsIt
and the time on the server would be returned
myserver.GetClientsList
and a list of the clients (the details "name, address, etc." of which are
defined by the server) would be returned
myserver.GetClient(12345)
and information related to clientID 12345 would be returned
To be clear the client would not control the format of the returned data.
The server has certain information available, it publishes the format that
it will be in and the client simply requests it.
Additionally the server should accept information (for example):
myserver.UpdateClient(ProperlyFormattedClientData)
I'm probably just describing a "server" (sorry about that but everybody asks
"what do you want to do")
So it could be done with a webserver I suppose, it could be done with DCOM
right? It could be done with services that .Net have introduced I'm sure
but some solutions are hard, some cost a lot, some are very limited, some
are proprietary, etc., etc. I was hoping for cheap, fast, powerful, easy
and non-proprietary![Smile :-) :-)](/styles/default/custom/smilies/smile.gif)
Is this a good place for such discussion? If not anybody have an idea where
a good spot would be? I'm looking for a discussion rather than a heated
argument.
Thanks,
Tom
server could be implemented. So the upsides and downsides can be discussed.
In case I'm using the term wrong by "app server" I mean a centralized
"business information service" that could be readily accessed by client
software. Initially this would be on a LAN but (like everything) the
requirements would likely grow to permitting general Internet access.
It shouldn't require .Net to exist on the client and ideally it shouldn't
even require .Net to exist on the server. I'd like to use .Net to write it
but it doesn't "have to" hook into everything that .Net offers. I'd just
like the ability to accept requests for information and send it back.
(Don't know if I should go on until I get a response... but I probably
haven't provided enough information yet... so)
Generally speaking the server would return data fetched from a database but
of course where the information came from shouldn't be important to the
client requesting it. So let me provide a few simples examples. Naming the
server "myserver" it should be possible to request the following (but not
necessarily using this syntax):
myserver.WhatTimeIsIt
and the time on the server would be returned
myserver.GetClientsList
and a list of the clients (the details "name, address, etc." of which are
defined by the server) would be returned
myserver.GetClient(12345)
and information related to clientID 12345 would be returned
To be clear the client would not control the format of the returned data.
The server has certain information available, it publishes the format that
it will be in and the client simply requests it.
Additionally the server should accept information (for example):
myserver.UpdateClient(ProperlyFormattedClientData)
I'm probably just describing a "server" (sorry about that but everybody asks
"what do you want to do")
So it could be done with a webserver I suppose, it could be done with DCOM
right? It could be done with services that .Net have introduced I'm sure
but some solutions are hard, some cost a lot, some are very limited, some
are proprietary, etc., etc. I was hoping for cheap, fast, powerful, easy
and non-proprietary
![Smile :-) :-)](/styles/default/custom/smilies/smile.gif)
Is this a good place for such discussion? If not anybody have an idea where
a good spot would be? I'm looking for a discussion rather than a heated
argument.
Thanks,
Tom