1.1 --- a/VSs.h	Wed May 23 13:17:07 2012 -0700
     1.2 +++ b/VSs.h	Thu May 24 07:34:21 2012 -0700
     1.3 @@ -29,9 +29,24 @@
     1.4  /*This header defines everything specific to the VOMP semantic plug-in
     1.5   */
     1.6  typedef struct _VOMPSemReq   VOMPSemReq;
     1.7 -typedef void  (*PtrToAtomicFn )   ( void * ); //executed atomically in master
     1.8 +typedef void  (*VSsTaskFnPtr )   ( void * ); //executed atomically in master
     1.9  //===========================================================================
    1.10  
    1.11 +#define IN    1;
    1.12 +#define OUT   2;
    1.13 +#define INOUT 3;
    1.14 +
    1.15 +typedef struct
    1.16 + {
    1.17 +   VSsTaskFnPtr fn;
    1.18 +   int32  numArgs;
    1.19 +   int32 *argTypes;
    1.20 +   int32 *argSizes;
    1.21 + }
    1.22 +VSsTaskType;
    1.23 +
    1.24 +
    1.25 +
    1.26  /*Semantic layer-specific data sent inside a request from lib called in app
    1.27   * to request handler called in AnimationMaster
    1.28   */

     2.1 --- a/VSs_Request_Handlers.c	Wed May 23 13:17:07 2012 -0700
     2.2 +++ b/VSs_Request_Handlers.c	Thu May 24 07:34:21 2012 -0700
     2.3 @@ -64,26 +64,11 @@
     2.4  
     2.5  
     2.6  //===========================================================================
     2.7 -/*The semantic request has the receiving processor and the message type
     2.8 - *
     2.9 - *Note one value in this approach: without the extra VMS layer,
    2.10 - * the send and receive would happen in real time instead of virtual time,
    2.11 - * which would waste real time while one of them waited for other
    2.12 - *
    2.13 - *When successfully pair-up, transfer ownership of the sent data
    2.14 - * to the receiving processor
    2.15 - *
    2.16 - *Messages of a given Type have to be kept separate..  so need a separate
    2.17 - * entry in the hash table for each pair: receivePr, msgType
    2.18 - *
    2.19 - *Also, if same sender sends multiple before any get received, then need to
    2.20 - * stack the sends up -- even if a send waits until it's paired, several
    2.21 - * separate processors can send to the same receiver, and hashing on the
    2.22 - * receive processor, so they will stack up.
    2.23 +/*
    2.24   */
    2.25  void
    2.26 -handleSendType( VOMPSemReq *semReq, VOMPSemEnv *semEnv )
    2.27 - { SlaveVP   *sendPr, *receivePr;
    2.28 +handleSubmitTask( VOMPSemReq *semReq, VOMPSemEnv *semEnv )
    2.29 + { SlaveVP   *sendPr;
    2.30     int          key[] = {0,0,0};
    2.31     VOMPSemReq *waitingReq;
    2.32     HashEntry   *entry;