Save Session Data to Database by Default

[Darwin Bautista]

Hi all,

Last year, we've run into problems regarding the session data becoming
so big that voters can no longer cast their ballot.
That said, can we just save the session data to the database by
default like we did in Feb 2009?
This will make the behavior of the system more predictable regardless
of the browser used (MS IE vs Firefox).

-Darwin

[Waldemar Bautista]

On Mon, Jan 24, 2011 at 1:24 PM, Darwin Bautista <dar...@gmail.com> wrote:
> Last year, we've run into problems regarding the session data becoming
> so big that voters can no longer cast their ballot.
> That said, can we just save the session data to the database by
> default like we did in Feb 2009?

Yes, I agree. That way, forgetting to configure the session database
will not cause problems.

--
Waldemar Amado Bautista

[Darwin Bautista]

Okay. I'm going to make this the default in the Halalan UP repo for
now since the DB in the main repo is different.
But I think that we should make this the default in the main repo
after things have stabilized since the CAPTCHA data is also stored
using CI sessions.

Yeah. I also noticed that the CAPTCHA data is being stored using CI
sessions, which is a big security hole

[Waldemar Bautista]

On Mon, Jan 24, 2011 at 1:46 PM, Darwin Bautista <dar...@gmail.com> wrote:
> Okay. I'm going to make this the default in the Halalan UP repo for
> now since the DB in the main repo is different.
> But I think that we should make this the default in the main repo
> after things have stabilized since the CAPTCHA data is also stored
> using CI sessions.

Okay.

> Yeah. I also noticed that the CAPTCHA data is being stored using CI
> sessions, which is a big security hole

In CI 2.0, the CAPTCHA plugin is converted to a helper and the data is
now stored in the database. I think we can use it in Halalan 1.x.x.

--
Waldemar Amado Bautista