>> >> I'll think you are clear to go onto the next phase if you are willing. >> I think you have an option. Do write or do access control. Write will >> be more exciting, access control will be more thought intensive. You >> may already have most of the write code, as you just wrote 100M items! >> >> Which one ? >> > > I do have codes which writes to cassandra. But if you are OK, I would like > to go with read with access control first. Writing I can easily in > cooperate to a sling interface once realized the API. I am not sure the > complexity of access controlling thing :-) . So better to start with it :-) > >
Thinking about it some more: Doing access control correctly is non-trivial, so much so we have had several long discussions on dev@ already. I am conscious of the time left on GSoC and think it would be better to use what you have learnt about write to implement the create and update methods on the CassandraResource. If that really is quick then there will be time to dive into implementing ACLs. I think that will eliminate one of the project steps (read ACLs) and replace it with read and write ACLs at the end, which means you may be able to achieve everything you set out to at the start of the project. Is that Ok ? Ian
