Re: Status and DB binding

Hello,


I'm glad to hear answer, because I imagine jRPM to be more then just
a java port of rpm too. I see a lot of useful features jRPM could
provide. So, why do not just start with describing its' key features?

Speaking in terms of UP we should first create a Vision of
project and use-case model. Then we will be able to develop Design
Model. I believe, it will not take much time, but these artefacts will be  
very
useful.

What do you think about it?


On Mon, 11 Apr 2005 19:34:13 +0200, Michael Kuß <[email protected]>  
wrote:
> Hi,
>
> I'm a little anoyed about myself about the status of jRPM.
> jRPM supports at the momen no db backend. Paul may be right to try
> it with sleepycat jni to get the stone rolling.
> My intention was to implement the reading of a pure RPM file first.
> There I got stuck somewhere on the path. But the most information
> can be read from the file.
> The next step would be to implement the db (as I see).
> Also the idea of implementing a web interface where you can upload
> rpms and distribute them to a community is most appealing to me.
> Also I would like to refactor a bit and maybe intoduce nio for
> the extensive IO operations.
>
> As I said it's a little bit sad there is no such development in sight
> and I have no time. :(
>
> btw.:
> Sorry Nikita and Paul, no code example for db4-java here.
> Maybe I have lost it.
>
>
>
> Micha
> --


-- 

Nikita


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click