T
thomas
Hello All,
The question may seem to be trivial, but I found it really was not, and I am
hoping that someone who has done it could share his/her experience.
How do I share my web application among my clients so it "becomes", or
appears to be, part of their websites?
Example: application showing current weather reports or stack prices, my
clients could "incorporate" into their websites without actually hosting it.
In addition my service application needs to maintain client specific data.
Perhaps even list of each of my client users. You got the idea.
The obvious, simple solution is to create a separate copy of the application
for each client and configure accordingly. However, this is exactly the
solution I am trying to avoid. The reasons are obvious.
So, I think, the alternative is to:
1. tell my clients to setup subdomain forwarding with masking
2. check Request.UrlReferrer, perhaps within Session_Start event, and store
it in the session state
3. fill in Client Context data based on the Request.UrlReferrer, and keep in
the session state
My question is what are the potential problems with this approach?
The one I am aware of is that I will need a custom, smart
MembershipProvider, if I chose to use this mechanism.
Are there any better ways of sharing my service application?
Thank you,
Tomasz
The question may seem to be trivial, but I found it really was not, and I am
hoping that someone who has done it could share his/her experience.
How do I share my web application among my clients so it "becomes", or
appears to be, part of their websites?
Example: application showing current weather reports or stack prices, my
clients could "incorporate" into their websites without actually hosting it.
In addition my service application needs to maintain client specific data.
Perhaps even list of each of my client users. You got the idea.
The obvious, simple solution is to create a separate copy of the application
for each client and configure accordingly. However, this is exactly the
solution I am trying to avoid. The reasons are obvious.
So, I think, the alternative is to:
1. tell my clients to setup subdomain forwarding with masking
2. check Request.UrlReferrer, perhaps within Session_Start event, and store
it in the session state
3. fill in Client Context data based on the Request.UrlReferrer, and keep in
the session state
My question is what are the potential problems with this approach?
The one I am aware of is that I will need a custom, smart
MembershipProvider, if I chose to use this mechanism.
Are there any better ways of sharing my service application?
Thank you,
Tomasz