[HILTI] Spicy Parsing WebSockets - how to end a list
Fernandez, Mark I
mfernandez at mitre.org
Thu Jul 27 12:54:52 PDT 2017
>> if there is a way to have the sink data come back to the WS_Handshake
>> unit after it is parsed by the Sub and WS_Messages units? (I'm thinking
>> it can't since it is already parsed.)
I encountered this dilemma too, but did not find a way around it. In WS_Handhake, you can reference self.wss_data, but it will be just a byte array, will not have structure or format to it. That is my experience, but I am new to spicy, don’t know all the tips or tricks.
From: Jennifer Gates [mailto:jenngates2004 at gmail.com]
Sent: Thursday, July 27, 2017 3:23 PM
To: Fernandez, Mark I <mfernandez at mitre.org>
Cc: hilti at ICSI.Berkeley.EDU
Subject: Re: [HILTI] Spicy Parsing WebSockets - how to end a list
I thought the sink would still keep the sub data as part of the original WS_Handshake unit and not a separate new unit. Otherwise, it does appear to be doing what I intended. Changing my code to how you suggested produces the same results.
I guess I'm just wondering if there is a way to have the sink data come back to the WS_Handshake unit after it is parsed by the Sub and WS_Messages units? (I'm thinking it can't since it is already parsed.) Or is there away to add the sub unit's ws_msgs field as a variable within the WS_Handshake unit, or somehow append the sub unit to the WS_Handshake unit?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HILTI