Re: [basex-talk] feature's requests and not publicly released features

Hi Fabrice,

thanks for your feature requests. Luckily, all of these are listed in our GitHub issue tracker. I can't give you any timeline yet.

How does BaseX team provide non-open-source features ?

BaseX itself will stay open source, no doubt about that. All of our commercial offerings are built on top of our free software, and we are glad to have a great community that helps us to improve the software and keeps it suited to all kinds of real applications.

In the context of commercial projects, we are often developing new features that are tailored for the particular task and environment. Development of such features takes much less time and resources than providing features for the wide public, as we need to

a) provide an architecture as generic as possible, b) properly document all the features, and c) react on (very valuable, but time consuming) feedback.

This is the reason why usually some time passes until new features make it to the public. Of course, we also have to convince customers that it's a good decision to make features public that they have been sponsoring, but usually it's fine with them, because all features that are part of the open source software will automatically be updated with every new release.

And of course, beside us, everyone else benefits from parties who are willing to pay for so-called "sponsored features", which are treated with higher priority. If you - or anyyone else - is interested in financially supporting the development of features, we invite you to contact us.

Thanks, Christian

On Thu, Mar 20, 2014 at 10:23 AM, Fabrice Etanchaud fetanchaud@questel.com wrote:

Dear all,

First of all, BaseX is just fantastic !

Could you please tell me if you may release the following features in near future ?

1.   User defined indexes
   
   
   
   

Let's consider you have to index multi lingual documents.

Currently, one have to partition each document in mono-lingual documents, and add them in separate collections because there can be only one fulltext index per collection, and because all text() nodes will be indexed.

Are others BaseX users interested with user defined indexes (attribute, text, and fulltext) ?

Wouldn't user defined indexes dramatically improve performance (during requests, and optimization) ?

2.   Break current collection limitation on the maximum number of nodes.
   
   
   
   

3.   Possibility to store millions of small documents, and do  efficient
   

'db:replaces' or 'db:delete'.

Last,

How does BaseX team provide non-open-source features ?

Best regards,

Fabrice Etanchaud

Questel/Orbit

---

BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk