 The speciality here is, and that's the hard piece for me now for my colleagues is we have object-based storage. It's not file-based, it's object-based storage. So you have the chance to store metadata in it, you have the chance to apply policies, etc. So that's a big change in the mind of my colleagues because all they want to do is to store their files. And now with cloud storage, it's not that easy. That's the drawback right now. We have an API, we have a good solution, but we don't have the applications yet. The in-nailbers, the connector, or how you want to name it, this is still missing right now. But the end-users or the applications, they develop now against the API. So the ones that made the mind-shift already, they are absolutely happy with it. The others, they have to do the mind-shift. You're talking about a whole new perspective on adding business value because you can apply metadata principles, you can apply policies, and so forth. You said the ones that have done that and exploited the architecture more fully are really happy. Can you give us some examples so we can sort of visualize that? So, you mean in terms of policies? Yeah, well you said that there's a capability now with object storage that you didn't have before, and some people have taken advantage of it, certain applications, can you share what examples there might be? So for example, you can store a policy which means important. If this object is important or not, based on this, then you can apply a policy which means I need one local copy, I need a major copy, or I need the geo-parity. So that's one of the things. And also age-based policy, for example, I can say delete this object after 30 days, and this is something they will implement with the 2.0. So you have an age-based policy which automatically deletes the object, and that's totally new for them.