[ebxml-iic] RE: impl guidelines,on the "technical" and "deployment" sides

Implementation Guideline Survey:
-------------------------------

Any suggestion / recommendation on any of the following points 
is welcome. Even a short paragraph / sample material is fine. 
You do not have to give away your implementation competitive, 
but think in terms of what may facilitate interoperability / standardization 
of implementations for testing and trouble shooting purpose. 

1. MSH General

(a)- MSH Configuration. 
(Any suggestion/recommendation? What format is used? Sample file? 
Expected content / scope of the configuration? What aspects of the CPP
will that also cover? Can it be done through API? …)

(b)- Application interface. 
(Advices on what should be in an MSH interface for the application layer. 
Comments on how to handle received messages? callback vs. “pull”...?)

(c)- Error logging. 
(Advice on what to do with errors messages received / generated ,  
Other errors / warnings that do  not translate in messages: 
logging format ( e.g. Log4j - and examples)? 
How unsupported/uninmplemented features are notified to partners?)

(d)- Web Server connection. 
(Implementing using servlets, thread considerations, servlet-engine 
specifics, etc.)

(e)- Message persistence. 
( required functions? Scalability issues? Database / file / message queue. )

(f)- MSH Version management. 
(How to facilitate the transition to a new MS version? Implement an 
MSH supporting two versions?)

(g)- ID generation 
(message ID, conversation Ids, SOAP extension ID)

(h)- Timing management and computations (timeouts, handling time zones)

(i)- What are the third-party software and utilities used to complement
the MSH functions? (Security? Persistence? ID generation?)

(j)- Others?

2. Any recommendation on the implementation of particular MSH Features:
(e.g. using specific language packages: Java libraries, multi-threading, etc.)

- Message Envelope, XML parsing
- Security
- Reliability (Duplicate search, Timeout mechanism)
- Status Messages
- Ping Service
- Message Ordering (management within a conversation)
- SyncReply (transport connection management)
- Multi-Hop
- Protocol Bindings
- …