[WG: Sakai QA] 2.8 proposed changes, etc. for discussion

[Hedrick Charles]

One thing worried me about the 2.8 proposed changes. It proposes putting sakai.properties in a database, if I understand it. Unless there's very careful caching this has a potential for seriously affecting performance. Properties are checked a lot. The current approach is fairly efficient.

I have a JSP for updating properties in the real time. That gets rid of the most serious problem with the current implementation. It wouldn't be hard to make that into a real admin tool. (Of course some tools read properties at starrt, and might not even work properly if you change properties in midstream. So you have to be careful. But that's true with the database as well.)


On Sep 3, 2010, at 10:32:43 AM, Jean-Francois Leveque wrote:

> I wonder why it was released with 2.6. Got warnings at the Paris 
> conference about blog in 2.5 but wasn't told anything for 2.6. :(
> 
> So, the official 2.8 might not have a blog.
> 
> Should I get in touch with Lancaster now?
> 
> J-F
> 
> csev a écrit :
>> -1 It also is sitting right there in SVN, easily checked out for anyone who needs it.
>> 
>> /Chuck
>> 
>> On Sep 3, 2010, at 9:21 AM, Anthony Whyte wrote:
>> 
>>> -1   Blogger was deprecated because it receives zero support from the Community and has a long history of security vulnerabilities.  The community has been warned via the deprecation mechanism and has  a full year to prepare for its removal in 2.8.  Leaving unsupported code in the release that is no longer a focus of QA activities raises the 2.8 risk profile unnecessarily. 
>>> 
>>> Anth
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
> 
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"