Hi...
Before I suggest some thing I have few questions....
1. Will users would be connected in network?
2.Will client having Windows XP would have network connection?
3. Are you developing intranet application or internet based application?
If your requiremtnts needs that users need to certain functions on
dis-connected mode and can do "certain" business logics after connecting to
network then I would suggest for a Smart Client Application.....
Let me know the scenarios of both users may be I can suggest you better
HTH
With BEst Regards
Naveen K S
[quoted text, click to view] "rob" wrote:
> In that case I guess I have a serious problem with my approach. As I
> said I would like to have two versions of my program. One will work in
> a server-client role. The other one as a standalone program. My plan
> was to write a server-client app and then the standalone program just
> has the server and client on the same machine. Of course if web
> services require IIS this won't work on Windows XP Home Ed, etc. Do you
> have any suggestions on how to best address this problem?
>
> Best Regards,
> Rob
>
Naveen,
Thanks for your reply. Here are the two scenarios.
There are multiple users all of them working with the same data. In
this case a server-client approach is chosen. The solution might be
deployed on an intranet or internet. The client has some complex
functions so I need a "rich" client.
If there is only one user it makes no sense to require him to have a
server. The user also might not want to host his data on an external
server. Nevertheless, he might (or might not) still connect to a server
for a data feed.
In both scenarios the users should be able to do some (limited) work
even when they are not connected to the server.
For the second scenario I do not want to write a seperate application.
So I was thinking of simply putting the client and server on the same
user machine. There are a few problems with that, though.
1) The user does not have MSSQL. I might just use MSDE for the second
scenario.
2) The user does not have IIS. This is a problem because I wanted to
use web services on the server to supply the client with data.
3) There might be some problems with authentification, authorization,
etc.
Any input on this is highly appreciated.
Regards,
Rob
Hi Rob,
Well....I would suggest you to build a Smart Client Application with SOA
approach.
Have Presentation, Business logics [some] on client.....use MSDE through
data access layer to connect Database on server......have important business
critical business logics or functions which might need other users input
deployed on server as webservices so that client consumes that .....
I hope this helps
With Best Regards
naveen K S
[quoted text, click to view] "rob" wrote:
> Naveen,
>
> Thanks for your reply. Here are the two scenarios.
>
> There are multiple users all of them working with the same data. In
> this case a server-client approach is chosen. The solution might be
> deployed on an intranet or internet. The client has some complex
> functions so I need a "rich" client.
>
> If there is only one user it makes no sense to require him to have a
> server. The user also might not want to host his data on an external
> server. Nevertheless, he might (or might not) still connect to a server
> for a data feed.
>
> In both scenarios the users should be able to do some (limited) work
> even when they are not connected to the server.
>
> For the second scenario I do not want to write a seperate application.
> So I was thinking of simply putting the client and server on the same
> user machine. There are a few problems with that, though.
>
> 1) The user does not have MSSQL. I might just use MSDE for the second
> scenario.
>
> 2) The user does not have IIS. This is a problem because I wanted to
> use web services on the server to supply the client with data.
>
> 3) There might be some problems with authentification, authorization,
> etc.
>
> Any input on this is highly appreciated.
>
> Regards,
> Rob
>
Don't see what you're looking for? Try a search.
