K
Kai Fransson
I am considering developing an online security service in the form of a web
application. However, because customer's security information would be stored
on my servers I am unsure if this will be accepted. Perhaps customers want to
run the application "in-house" so that their data is stored locally. I am
convinced however, that some customers will want/accept the fact that their
data is stored on my servers.
This makes me unsure wether to develop a regular ASP.NET+Silverlight
application, or if I should choose something that users can also deploy and
use "in-house". Is there a techonology (or perhaps a design pattern) that
would help me accomplish both?
application. However, because customer's security information would be stored
on my servers I am unsure if this will be accepted. Perhaps customers want to
run the application "in-house" so that their data is stored locally. I am
convinced however, that some customers will want/accept the fact that their
data is stored on my servers.
This makes me unsure wether to develop a regular ASP.NET+Silverlight
application, or if I should choose something that users can also deploy and
use "in-house". Is there a techonology (or perhaps a design pattern) that
would help me accomplish both?