Hi Tab, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to [email protected] and follow simple instructions in the reply.
Tab Spangler wrote > (1) Are the Clients truly clients of the cluster? It appears as if the > clients are actually cluster members in that they share cluster heartbeats > and other coms inside the cluster. My concern here is that if we have > clients on desktops in many different offices this may cause a problem > with networking and so on. What I don't want is lots of these "Clients" > dropping in and out of the cluster and causing membership changes, because > we're stretching the cluster network geographically. Clients are members of the cluster, because they are not just thin clients but provide full API set which is the same as for embedded server nodes. However, clients use different discovery protocol which protects them from issues you described. Tab Spangler wrote > (2) As I said we're looking to have 100's of clients in offices all over > North America, has Ignite been used before in this type of topology? Yes, there are example of successful usage in similar scenarios. It's not very typical though, so can require some tuning. Tab Spangler wrote > (3) My other concern is that the .NET client seems to be a wrapper around > the Java client, is there an option to use a pure .NET client or do we > have to ship a JVM with the .NET client? .NET client is wrapped around Java implementation to provide fully-pledged platform instead of limited thin client. JVM is required to run .NET client. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Questions-on-Ignite-Clients-tp10304p10321.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
