Looks like a web service.
I would see something like :
- application A ask B for a value
- if no value available brings up app B (possibly asking first the user)
- once B is closed A can get the value (through a web service)
It may still need some more thoughs (what annoys me a bit is that it's seems
it should be tied together from an UI point of view). How to decide app B
needs to be launched especially if there is a previous result available ?
Can't the user decide to launch B at will ? App A will have the last result
created in B...
Are A and B really distinct apps ? (for example an intranet like application
could use a single data store, making all data available to all "modules" as
needed).
Patrice
"arkam" <ar***@caramail.com> a écrit dans le message de
news:e1**************************@posting.google.c om...
Well you are right I have to explain a little more :
- One user starts application A.
- application A needs application B and then starts it (via
response.redirect for example)
- the user uses application B
- when finished, application B should bring application A back and
transmit it the result of what the user made
- application A comes again containing the data the user entered in
application B
Any idea ?
"Patrice" <no****@nowhere.com> wrote in message
news:<#b**************@tk2msftngp13.phx.gbl>...
Describing why you want to do that may also help. For now I would say a
web service ? (other options I can think off are using the querystring, or a
shared database if reachable by both apps).
Patrice
"arkam" <ar***@caramail.com> a écrit dans le message de
news:e1**************************@posting.google.c om... Well everything is in the title !
Arkam
