Re: NodeJS thin client: full API
Alexey, I'm trying to get Enum from cache which placed by different thin client and find that i can't get it, only exception And more when im trying to get Enum which is placed by nodejs client i also can't do it, have same exception code and output - https://gist.github.com/pilshchikov/ca9fda160e310f62dd4d1d6dbb2f904c Can you please help me to investigate it, maybe something im doing wrong, because its look like a bug -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Python thin client
Hi, all Tried to compare new thin client performance and made similar benchmarks for each one And result not so good for python Ticket with results and bench code: https://issues.apache.org/jira/browse/IGNITE-9824 Py code src: https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb Dmitry, please review results and bench code, maybe somthing wrong or it's expected numbers? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: PHP thin client
> You know, I'm confused with all this documentation stuff... > For nodejs client all docs were moved from the repo to readme.io but the > readme.md keeps the installation instructions (duplicated with > readme.io). Probably, that's ok. > Will add similar short readme.md to the PHP PR. Its good What i think (and how it partially now): All user documentation should be on readme.io (how to install, use it, configurate, description for examples) All developers documentation (how to release, how to start develop) and(!) basic description should be in repository -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: PHP thin client
> 1. Because finally the docs should not be in the repo (unfortunately) but > on readme.io. > There is a task for that: > https://issues.apache.org/jira/browse/IGNITE-9523 > Added the link in the jira. Ok > 2. Examples in readme.md are more like code snippets (mostly not big) > intended to help better understanding the usage of the client along the > reading. > Examples in php/examples are more meaningful and fully cover the > examples in readme.md. Oh, now i get it But now in PR we have no readme at all Agree with examples on readme.io, but other information (how to install, how to configurate, install from sources, basic description) may be in sources, it help a lot Or it also should be on readme.io? This question because in other platforms have readme exist and they have this basic information in it -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: PHP thin client
Sorry for interruption but im also review this feature and have couple questions about documentation 1. Why exists second branches with all documentation? I mean they looks good together, why need to separate? Also, one place when i found this branch it is this thread, not in jira, not in a github 2. Examples in readme.md have better look in php/examples. I mean php/examples have one set of examples and readme have second one, they not match and they both looks good. Why doesn't add readme examples in php/examples? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
