Thank you, Matthieu.
>> * Is the name “product” set in stone? Would it be possible to call >> it a “profile” for example? > > I don't really care. I don't really like "product" name. Maybe > "profile" is better but I'm not sure. Ok, thank you. So unless somebody raises an objection, I will go with “profile”. (En passant, même en français, en regardant la définition Larousse, “profile” me semble être tout à fait raisonnable.) >> * (Guice + Cassandra + RabbitMQ + Swift + ElasticSearch) —> >> Clustered >> * (Guice + Cassandra + ElasticSearch) —> Advanced >> * (JPA + Lucene) —> Basic > > Is "Distributed" to ambiguous for you (instead of Clustered)? No, “distributed” is just fine. I will make the change. >> - Uses Cassandra, RabbitMQ, Swift, and ElasticSearch behind the >> scenes > > We support S3 too and we'll probably talk to Swift via S3 protocol > soon. Also, more people understand S3 than Swift or even Object > Storage. I would than replace Swift with S3 in that description. Ok, no problem. >> - Uses JPA + Lucene behind the scenes > > I really don't like using JPA in product/profile description. I'd > rather describe where data is store. > > As you may have read, we have one product/profile using derby (embeded > database using local filesystem) and another using mariadb/myql. Ok, so how about either “file system” or “RDB”? >> It would be great to also have a “minimal” Profile that uses the file >> system and a minimal number of dependencies, if possible. > > It's JPA with derby. Sure, that works. Unless somebody has something else to add, I will create a new PR for this section of the documentation, and we can continue the discussion there. Cheers, =David --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
