[ebxmlms-develop] Some thoughts regarding transport...

[Daniel B. <Dan...@os...>]

Hi,

I noticed some changes in hk.hku.cecid.phoenix.message.transport.Http
regarding server authentication... I recently had to change this file =
myself
with a few hacks in order to make it suite my environment.

There is a lot of configuration that can be done on an outbound =
connection
and I guess this class is going to be a hot spot for changes in the =
future.
So why don't make the hole lot pluggable? The plugin could take an
ebxml-message and return an HttpURLConnection (the actual sending of =
the
message still being done in Http.java). This way the user could =
control:

* The implementation of the http-protocol (The rather strange hack for
forcing which implementation to use in the beginning of send wouldn't =
be
needed)
* The plugin could use different setting (hostname verifiers, proxy
configuration etc.) for different trading partners, which would be very
useful.
* Resolving partner uri:s to URLs could be deferred to this point (a
separate plugin for that wouldn't be needed)
* The user doesn't have to rely on system properties to configure =
outbound
connections. (System properties are great for stand alone applications, =
but
not for application servers!)

It also would be nice if there was a way of passing configuration
information to plugins. One suggestion is to give the plugins a method =
that
takes an 'Element' from the xml in the configuration file...

If you like the id=E9a and need a hand with the implementation I'd be =
glad to
help you...

regards

Daniel