below:
I'm pleased to see Avalon adopted by a growing number of projects,
but now I'm starting to wonder about the service definition, as each
one defining it's own service (e.g. authentication) doesn't help
integrating components coming from various origins. Time for a more
formal Avalon service repository ?
I think that would definitely be a good idea. Keel's central theme is
"don't get tied to any particular implementation, look around and use
the best, perferably OpenSource, implementation and make a component
out of it". So, we are definitely all for a common service repo. from
which everybody benefits. A service repository would help,
definitely, by not everybody always having to rethink the interfaces.
I wanted to browse the archives and wiki, but this requires prior
registration, which will obviously refrain many people going further...
I am copying Pete C......let's see if he can open that up possible...
Email list done, wiki always was open I think.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
