![]() |
Telelogic TAU (steve huntington) | ![]() |
Topic Title: Dynamically creating multiple instances for unicast Topic Summary: Unicast to an instance Created On: 20-Oct-2006 20:31 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thanks Ian, this is the method I have been using! Best Raman | |
![]() |
|
Hello, -------------------------------- ------------------------- Raman Edited: 20-Oct-2006 at 21:57 by Ramandeep Ahuja |
|
![]() |
|
![]() |
|
Raman
Both clients are using the same port, so the port can't be used to direct communication to a particular client. There are some options: 1. The Server sends the signal to a specific object (client) by e.g.: MyClients[1].sigToClient() or client1.sigToClient() in an output symbol 2. After a signal has been received by the server from a client, it can store the 'sender' value in an attribute and uses it to respond to the source of the signal, using the notation shown in 1 above, e.g. (assuming the sender was stored in an attribute theClient) theClient.sigToClient() 3. The definition of the signal sent by the client to the server includes a PID value; the client includes its identity (this) in the signal it sends to the server, which uses it to respond, using the notation shown in 1/2 above. In general option 2 or 3 is likely to be preferable because it is up to the clients to request service from the server, which responds to wherever the request came from. HTH Ian ------------------------- ============= Ian Barnard Principal Consultant Telelogic UK, an IBM company |
|
![]() |
|
![]() |
|
Thanks Ian, this is the method I have been using!
Best
Raman
------------------------- Raman |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.