[Registry-dev] Registry next release and road map

[Sanjiva Weerawarana]

Deepal Jayasinghe wrote:
> In 0.1 release we tried to cover most of the features that we wanted to
> have there. However for the there are a number of items left for the next
> release , in my view we need to address those while keeping the code as
> stable as current release. So following are the list of items that I have

+1.

> in mind and all those are open to discuss and finalize what we need and
> what we do not  need.
> 
> - Need to have more documents describing
>     - Remote registry and how to use that
>     - Registry user management and how it works
>     - More descriptive user guide to use the UI
>     - Explain how to use and configure data sources

+1 - let's spend some time next week planning the docs and then get 
cracking on it immediately.

> - Basic Authentication support for remote registry

Now in progress.

> - Utility or tools for file import and export

+1 to make the import/export stuff into command line utilities.

> - Availability to switch registry implementation from the UI

+1.

> - Separate UI part from the core web and try to release that separately ,
> so that any one can use that to configure and access and kind of registry

+1 .. basically we need a registry-api.jar separately first and then the 
different impls separately. Users should be able to mix and match and get 
them to work.

Programmer level docs are critical too.

> - Enhance the support for WSDLs and XSDs

+1.

> - complete the i18n support

+1 for doing this right once and for all.

> - Do a performance bench mark to figure out the amount of data and the
> size of resource that the registry can handle.  Specially memory and CPU
> utilization.

+!.

> - ???

- Caching support

As discussed yesterday- proper support for HTTP client-side caching .. via 
If-Modified-Since first (as that's trivial for us) and then via ETag: 
header support. Doing just I-M-S is really sufficient too as either 
technique enables full client side caching.

Per our conversation the plan is to only do this for the actual resources 
accessed via /resources/*.

- [OPTIONAL] webdav support

This is totally optional .. but would be cool to have :-).

Basically plug in the webdav servlet from tomcat under /webdav and support 
at least read-only resource access thru that. Advantage? We can "mount" 
the registry as a file system then in Windows (and I'm sure in Linux). Why 
bother? If you have Google desktop search then (I believe) you can get it 
to index that .. thereby giving you Google search over a private registry 
on your machine. This is part of my personal need for a file system 
replacement - I'm looking at the registry as a personal file system 
replacement basically.

> I know if we are going to implement all those we need more time so need to
> prioritize the  items and need to come up with proper release plan when we
> are going to do the release.

Please develop a proper release plan for these features to be in 1.0.

Sanjiva.
-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: sanjiva at wso2.com; cell: +1 650 265 8311 | +94 77 787 6880

"Oxygenating the Web Service Platform."