search

inaes-tic / mbc-mosto

@mbc-playout's playlist juggler
GNU Affero General Public License v3.0
3 stars 5 forks source link

Replicate changes from mongo driver to json driver #37

Open jmrunge opened 11 years ago

jmrunge commented 11 years ago

Replicate all changes made to mongo driver into json driver, in order to keep them changeable.

xaiki commented 11 years ago

On 9 April 2013 09:03, Juan Martin Runge notifications@github.com wrote:

Replicate all changes made to mongo driver into json driver, in order to keep them changeable.

that is basically:

Niv Sardi

jmrunge commented 11 years ago

Agree!

Enviado desde mi BlackBerry

-----Original Message----- From: Niv Sardi notifications@github.com Date: Tue, 09 Apr 2013 09:18:06 To: inaes-tic/mbc-mostombc-mosto@noreply.github.com Reply-To: inaes-tic/mbc-mosto reply@reply.github.com Cc: Juan Martin Rungejmrunge@gmail.com Subject: Re: [mbc-mosto] Replicate changes from mongo driver to json driver (#37)

On 9 April 2013 09:03, Juan Martin Runge notifications@github.com wrote:

Replicate all changes made to mongo driver into json driver, in order to keep them changeable.

that is basically:

Niv Sardi

Reply to this email directly or view it on GitHub: https://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-16123173

Lacrymology commented 11 years ago

This depends on #44

xaiki commented 11 years ago

status?

On 11 April 2013 15:08, Tomas Neme notifications@github.com wrote:

This depends on #44 https://github.com/inaes-tic/mbc-mosto/issues/44

— Reply to this email directly or view it on GitHubhttps://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-16251569 .

Niv Sardi

jmrunge commented 11 years ago

Status @Lacrymology ? I think #44 was solved already...

Lacrymology commented 11 years ago

Do we keep the JSON driver?

xaiki commented 11 years ago

no if we have a replacement as a test harness to test the rest of the code.

On 17 September 2013 17:07, Tomas Neme notifications@github.com wrote:

Do we keep the JSON driver?

— Reply to this email directly or view it on GitHubhttps://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24618004 .

Niv Sardi

Lacrymology commented 11 years ago

hm, all I can say right now is that current tests go through 46% of mongo playlists driver, but nothing of json driver

I'm not sure what we're testing or not testing with(out) going through any playlists drivers.

Parts of the functional test (specifically the ones that depend on the playlist driver) are not running yet (because they will depend on changes in caspa)

jmrunge commented 11 years ago

I would like to keep the JSON driver. Its not only a way to test mosto, its also a way to easily use mosto without caspa.

2013/9/17 Tomas Neme notifications@github.com

hm, all I can say right now is that current tests go through 46% of mongo playlists driver, but nothing of json driver

I'm not sure what we're testing or not testing with(out) going through any playlists drivers.

Parts of the functional test (specifically the ones that depend on the playlist driver) are not running yet (because they will depend on changes in caspa)

— Reply to this email directly or view it on GitHubhttps://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24621982 .

xaiki commented 11 years ago

If it's only for mosto without caspa we let it die,... The overhead is toó high right now.

Again, either we do the same with our test harness or we fix it.

Niv Sardi, mobile. On Sep 17, 2013 11:38 PM, "Juan Martin Runge" notifications@github.com wrote:

I would like to keep the JSON driver. Its not only a way to test mosto, its also a way to easily use mosto without caspa.

2013/9/17 Tomas Neme notifications@github.com

hm, all I can say right now is that current tests go through 46% of mongo playlists driver, but nothing of json driver

I'm not sure what we're testing or not testing with(out) going through any playlists drivers.

Parts of the functional test (specifically the ones that depend on the playlist driver) are not running yet (because they will depend on changes in caspa)

— Reply to this email directly or view it on GitHub< https://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24621982> .

— Reply to this email directly or view it on GitHubhttps://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24637357 .

jmrunge commented 11 years ago

I think there is no overhead... let me take a look at it and write its test... it should not take more than 2 hours.

2013/9/18 Niv Sardi notifications@github.com

If it's only for mosto without caspa we let it die,... The overhead is toó high right now.

Again, either we do the same with our test harness or we fix it.

Niv Sardi, mobile. On Sep 17, 2013 11:38 PM, "Juan Martin Runge" notifications@github.com wrote:

I would like to keep the JSON driver. Its not only a way to test mosto, its also a way to easily use mosto without caspa.

2013/9/17 Tomas Neme notifications@github.com

hm, all I can say right now is that current tests go through 46% of mongo playlists driver, but nothing of json driver

I'm not sure what we're testing or not testing with(out) going through any playlists drivers.

Parts of the functional test (specifically the ones that depend on the playlist driver) are not running yet (because they will depend on changes in caspa)

— Reply to this email directly or view it on GitHub< https://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24621982> .

— Reply to this email directly or view it on GitHub< https://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24637357> .

— Reply to this email directly or view it on GitHubhttps://github.com/inaes-tic/mbc-mosto/issues/37#issuecomment-24660438 .