In contrast, an IM that isn't a one-off message says, "If you're there and available, I would like to have a real-time chat with you." Each mode of communication sets different expectations. It's quite handy. If you unify everything into a single mode of communication, then you have to set expectations explicitly.
"Hi, Joe. Can you tell me XYZ? Please reply when you are available to have an interactive real-time conversation with me."
"Hi, Joe. Can you tell me XYZ? Please reply at your leisure. I may not be available immediately to discuss your reply but will respond at some point if I have further questions."
See the difference? Of course, the different modes of communication don't mean the same things to everybody. I expect every company and every group of friends has a slightly different IM culture, for instance.
It's not even remotely uncommon for people in my circle to leave an IM or even a group chat in the middle. We all have dozens of things going on at any given time and it's expected that, unless the conversation is Really Important it will take second fiddle to the emergency of the moment.
So for us all conversations implicitly fit into your second category unless pretty explicitly stated already.
I concede, however, that if your typical behavior doesn't fit this model already wave is likely to be somewhere between useless and actively frustrating.
I don't have email interactions or IM interactions, I have conversations. I frequently switch off an email chain to an IM or telephone or even in person. If wave lets me coordinate that all in one interface and let me access the same history and context from multiple locations it will be phenomenally useful for me.