I've been thinking about something: how can custom business objects in shared assemblies/libraries/components/etc. within the context of a multiplatform application, wherein XMPP is used, be preserved? In other words, if an app uses .NET or J2EE or Python, a truly componentized hierarchy should be available so a component can leverage messaging/presence data and not be bound over HTTP, XMPP, TCP. It's worth taking a serious look at making sure we make a consistent set of outlets for any web framework or one-off project to hook into as a means of marshaling data over common logical tiers and over desktop, mobile, web, e-mail, RIA, SMS, XMPP. Thoughts?
