Discussion Board

Results 1 to 2 of 2
  1. #1
    Registered User
    Join Date
    Nov 2005

    Help Needed:WSP and concatenated message

    I am really cofused by the fact that SAR happens to be occur at WTP layer but WSP has primitives that r strictly meant for concatenated messages. if WTP does all the Segmentation and Reassembly job then why primitives as S_MetohdInvoke,S_MethodInvokeData(with a "More Data" flag up) r there in the WSP layer.standards tell that WTP takes care of SAR at times of sending big files as MMS.Then what do these primitives do in WSP?I am really cofused Plz help.

  2. #2
    Registered User
    Join Date
    Sep 2004

    Re: Help Needed:WSP and concatenated message

    The WSP commands that your client sends are WTP Invoke messages. WTP Invoke messages are sent over WDP, and longer invoke messages (like the one for the WSP POST) might use WTP layer Segmentation-and-Reassembly (SAR) for transmission).

    The WSP responses that your client recieves are WTP Result messages, also sent over WDP.

    Once a session is established, the client can start exchanging data with the server using the SMethodInvoke and S-MethodResult primitives.

    A method transaction can only be invoked under the following circumstances:

    * the WSP session is in either the Connecting, Connected or Resuming state
    * the number of of outstanding method transactions has not reached the negotiated Method MOR

    Both these circumstances must be statisfied before a method may be invoked. Further, during the capability negotiations, the Protocol Option for Large Data Transfer may be refused (WSP Specification If this is the case, then the use of the S-MethodInvokeData (by the Client) and S-MethodResultData (by the Server) is forbidden.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts