jxstanford1
|
Posted: October 06, 2008 05:18 by jxstanford1
|
|
We had a picture on the board the other day of an async mechanism for the client proxy adapter to get a unique id to be used as a session id until the real client has been allocated a task id. I've got most of it sorted out. It goes something like: 1. CPA requests some # of unique session IDs from the ID generator (async call) 2. CPA listens for a response 3. ID generator sends the session IDs when they become available What I can't remember is how the ID generator knows where to send the session IDs back to. I can think of a couple options, but this is the most reasonable one: We register each CPA through adapter registration so the adapter has an adapter ID. Then the message will be sent back to the originating CPA by consulting the controller routing table. Do we need dynamic CPA registration or do we have a known number of each type of CPAs? Can anyone comment? Thanks, John |
Client proxy adapter design issues
1 post
Replies: 0 - Last Post: October 06, 2008 05:18
by: jxstanford1
by: jxstanford1
« Older Topic
» Newer Topic
showing 1 - 1 of 1
Replies: 0 - Last Post: October 06, 2008 05:18
by: jxstanford1
by: jxstanford1
« Older Topic
» Newer Topic
