Inter-application communication
-
I'm using single-sign on across multiple web apps, with Forms Authentication, and its all working very nicely. It has allowed me to make some little web apps that do not-much (update address details and such) and link to them from my bigger web apps, and not worry about anything else. It really is all roses.... BUT.... I would like to customize the look of the little web app slightly, depending on who is calling it. I can do this through the QueryString, but its kinda ugly. Is there any other way to do it? Obviously Application is out, since they are seperate apps. Session is a possibility, but i'd like to avoid it if necessary. What i'd love is if I could programmatically write and read to the master "web.config" in the wwwroot, but this is not possible. any ideas would be much appreciated --- Dave
-
I'm using single-sign on across multiple web apps, with Forms Authentication, and its all working very nicely. It has allowed me to make some little web apps that do not-much (update address details and such) and link to them from my bigger web apps, and not worry about anything else. It really is all roses.... BUT.... I would like to customize the look of the little web app slightly, depending on who is calling it. I can do this through the QueryString, but its kinda ugly. Is there any other way to do it? Obviously Application is out, since they are seperate apps. Session is a possibility, but i'd like to avoid it if necessary. What i'd love is if I could programmatically write and read to the master "web.config" in the wwwroot, but this is not possible. any ideas would be much appreciated --- Dave
Hi Dave. How about setting a cookie?
-
Hi Dave. How about setting a cookie?
Yes, that could work too... It just seems a bit wierd expecting the browser to carry my configuration info across the request. Actually Session would be okay I suppose, since the use gets a Session cookie anyway, but I think that a session is probably not valid across applications. --- Dave
-
I'm using single-sign on across multiple web apps, with Forms Authentication, and its all working very nicely. It has allowed me to make some little web apps that do not-much (update address details and such) and link to them from my bigger web apps, and not worry about anything else. It really is all roses.... BUT.... I would like to customize the look of the little web app slightly, depending on who is calling it. I can do this through the QueryString, but its kinda ugly. Is there any other way to do it? Obviously Application is out, since they are seperate apps. Session is a possibility, but i'd like to avoid it if necessary. What i'd love is if I could programmatically write and read to the master "web.config" in the wwwroot, but this is not possible. any ideas would be much appreciated --- Dave
Hi Dave, AFAIK, Sessions will not (really SHOULD not) function across applications. Why should App A. know anything about the sessions open on App B, after all? My first thought was: If these pieces of functionality are really this closely linked, are you sure they belong in two seperate applications? Especially if some of the "applications" are really simple. Second thought: develope a user-config architecture in a database and pass a userID between applications (do it in the querystring or cookie). This way, each application can use the user ID to look into the database and determine how to display various aspect of the screen. Hope this helps, Bill ps: web.config is for application level config settings. It's not an appropriate place for user specific items.
-
Hi Dave, AFAIK, Sessions will not (really SHOULD not) function across applications. Why should App A. know anything about the sessions open on App B, after all? My first thought was: If these pieces of functionality are really this closely linked, are you sure they belong in two seperate applications? Especially if some of the "applications" are really simple. Second thought: develope a user-config architecture in a database and pass a userID between applications (do it in the querystring or cookie). This way, each application can use the user ID to look into the database and determine how to display various aspect of the screen. Hope this helps, Bill ps: web.config is for application level config settings. It's not an appropriate place for user specific items.
Bill Dean wrote: If these pieces of functionality are really this closely linked, are you sure they belong in two seperate applications? Having two applications simply saves code updates. If I change the login form logic, I only need to do it in my login application. The applications that use it, get passed the User ID as normal, they need not care how that person was authenticated. Bill Dean wrote: web.config is for application level config settings. It's not an appropriate place for user specific items They arent user specific items, all users see the same thing, I just want to be able to easily change what that "thing" is. --- Dave