<slaps_head/>
Of course - "something else".
Two lessons learned:
1. Practice what you preach - no matter how excited you are to
play with a new technology, don't abandon Test First principals:
infinite loop in blip processing found in second unit test.
2. Log output in app engine console isn't written until request
finishes processing. If your request doesn't finish, you get no
logs :)
Well, that was embarrassing. I hope nobody reads this :)
A
On Oct 14, 9:31 pm, Andrew <[email protected]> wrote:
> Hi there,
>
> This is probably just a case of not having stumbled onto the key piece
> of documentation yet, but it's kept me confused for a few hours.
>
> I've written a robot that reacts to occurrences of text of the form
>
> something:[email protected]
>
> ... in the text of BLIP_SUBMITTED events.
>
> All is working nicely in the app when blip text contains *no*
> occurrence of something:[email protected], or *only* the text
> something:[email protected], but if the text contains
> something:[email protected] *and anything else*, the event never
> makes it into my robot AT ALL (as shown by the appengine logs).
>
> Have I just accidentally used a form of text that is reserved for
> something else or is there something else going on?
>
> Thanks,
>
> A
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Wave API" 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/google-wave-api?hl=en
-~----------~----~----~----~------~----~------~--~---
