Class-ifying objects is fundamental notion in the O-O universe. But so is encapsulation. If your code is not going to be using multiples of these message objects often throughout (I wouldn't call 3 or 4 times 'often'), then going to the trouble of rigorously class-ifying your objects may not be a useful return on your investment. Yes, you could come up with an interface definition that helps you to better class-ify your code, but is it worth the trouble, really?

What you have done that is wholly appropriate is to encapsulate the behavior of your objects using an idiom that you've come up with. It shouldn't be too hard to maintain this at the current level of usage.

Should you decide that this message object should be mutated and ubiquitous, then you might want to consider developing more O-O type software. Till then, I'd let it slide.

Drew

Be careful what you wish for... (Mr. Limpet)

For where you treasure is there shall your heart be also (Christ)