...
| Expand | ||
|---|---|---|
| ||
Currently this could mean making the current components more complicated. Or making another secure LLP component and mapping those LLP interfaces using secure sockets into the new component which supports SSL/TLS. |
| Expand | ||
|---|---|---|
| ||
We’re trying to hit the sweet spot of understanding the simple common set of usage that most people need. That way we can make simple components which are intuitive to understand in terms of their configuration and their implementation. Unusual requirements for a few interfaces shouldn’t come at the cost of making things complicated for everyone. Our design goal with IguanaX is to make simple components that work for most people out of the box. But when something more complicated is needed, to make it easy to crack a component open and easily modify it to meet the need you have. |
| Expand | ||
|---|---|---|
| ||
We are starting by working with some helpful customers who are willing to share their code from Iguana 6 so we start to get a picture of ‘what is normal?'. What is the set of components and configurations hits 90% of the use cases.? |