Sounds great, Glen. Thanks for the clarification (ie if you need access to the MessageContext, then just write your service as a Handler). Keep up the good work in cleaning all this stuff up.
BTW, this type of issue was somewhat representative of what I've (presumably others as well) found lacking in the documentation: the "whys and hows" with respect to architectural decisions. It seems that most of the docs are concerned with Java, client code, and RPCs and making simple examples work... Maybe I'm looking in the wrong places or just expecting too much. Anyway, thanks for your response! And it would be great if your explanation (below) found its way into the docs as an explanation of why the method signatures changed! -- Dan Kamins ----- Glen Daniels <[EMAIL PROTECTED]> wrote: Hi Dan: The issue with the MessageContext API is that it's just about identical to another pattern we already have, namely Handlers. Why not just make your service provider a Handler and use its invoke()? And even if you still do want to use the MsgProvider for some reason, you can always just call MessageContext.getCurrentContext() in your backend method. Sound OK? _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
