There's actually two interesting points to come out of your email.

The first is that the 'long' answer to your original question is that
the Wave Sandbox actually still supports an actual blip 'submit'
operation. We plan to remove this as soon as possible - although this
won't actually entail any changes to the way a user might access their
waves, or a robot will get notifications (since we'll just represent
this as a change to the XML). Watch this space.

The second point is that when this change is implemented this
information will be placed inside "some kind of envelope metadata"
which may not be immediately obvious from the sandbox client. So, you
were definitely on the right track.

On Mon, Sep 7, 2009 at 18:47, Eric Kidd<[email protected]> wrote:
>
> On Sep 7, 2:14 am, Sam Thorogood <[email protected]> wrote:
>> The short answer is no, it's not part of the protocol. The submission
>> of a blip is something interpreted from less specific modifications of
>> XML. However, this will be pretty easy to interpret and turn into
>> useful messages for a robot.
>
> Thank you for answering my question!
>
> When I look at the "Debug" > "Show all wavelets" display in the
> sandbox client, I can't see any difference between a pre-submission
> blip and post-submission blip. Are the "less specific modifications of
> the XML" that you mention stored in some kind of envelope metadata
> that I can't see in the sandbox client? Or am I just missing something
> really obvious?
>
> Thank you for taking the time to answer protocol questions here on the
> Google Group! I know the Google Wave team has some pretty brutal
> deadlines.
>
> Cheers,
> Eric
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to