bassa-devs Mailing List for Bassa Server
Status: Planning
Brought to you by:
wathsala
Menu
▾
▴
bassa-devs — Bassa developers talk here
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
|
From: Buddhika S. <bud...@gm...> - 2008-11-02 14:33:40
|
got it On Sun, Nov 2, 2008 at 12:18 PM, Wathsala Vithanage <wvi...@gm...> wrote: > This email is sent to test the mailing list. > > -- > wathsala > http://wathsalav.blogspot.com > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bassa-devs mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bassa-devs > > -- Bud THINKCube: Out of the box solutions in a box http://www.thinkcube.com Blog: http://geekaholic.org http://sinhalenfoss.org |
|
From: Wathsala V. <wvi...@gm...> - 2008-11-02 06:48:16
|
This email is sent to test the mailing list. -- wathsala http://wathsalav.blogspot.com |
|
From: Parthipan <lp...@gm...> - 2008-10-17 10:13:13
|
Hi all, Since more of us plan to use the repository, let's come up with a set of simple rules to follow. Couple of good tips are found at https://www.forge.funambol.org/scdocs/SVNTips. I think we should at least adapt the following rules from there. * Users commit their day-to-day work on /trunk. * Rule #1: /trunk must compile and pass regression tests at all times. Committers who violate this rule are publically humiliated. * Rule #2: a single commit (changeset) must not be so large so as to discourage peer-review. * Rule #3: if rules #1 and #2 come into conflict (i.e. it's impossible to make a series of small commits without disrupting the trunk), then the user should create a branch and commit a series of smaller changesets there. This allows peer-review without disrupting the stability of /trunk. Additionally: Rule #4: RC (Release Candidate) branches will be made when required (how exactly this consensus is achieved is another problem, but for now let the project lead decide that) and small bugfixes will be made in the branch and backported to the trunk. The RC branches will be stable in build and features and is recommended for users who want to build from source but not do any development. Cheers ~parthi |
|
From: Wathsala V. <wvi...@gm...> - 2007-10-09 05:18:26
|
Hi all, You can get the latest code developed during Google Summer of Code from SVN. regards -- wathsala http://wathsalav.blogspot.com |
|
From: Wathsala V. <wvi...@gm...> - 2007-07-11 11:20:43
|
Currently for previews Bassa uses this XML message <bassa> <file_name>Name of the downloaded file with extension</file_name> <origin_url>Origin URL of the content</origin_url> <cache_url>URL for the cached content</cache_url> <meta_content> <meta_content_url>URL of the meta content</meta_content_url> <mime_type>Mime type of the meta content</mime_type> </meta_content> </bassa> Above message is totally new to GADisk, so decoder should be written Notification message XML is also updated <file_name>Name of the downloaded file with extension</file_name> <status>completed or failed</status> <origin_url>The origin URL for the content</origin_url> <cache_url>The URL for the cached content</cache_url> <server_response>The response (http) from the origin server</server_response> <size>Length of the downloaded content</size> </bassa> This is an old message but <size> element is newly added. <status> cdata is now limited for 'completed' or 'failed' strings earlier it carried the response of the origin server (separated by a space). Now the origin server response is in the new tag <server_response>. The origin URL of the content was in <rurl> tag, now the tag is renamed to <origin_url>. The tag <cache_url> was not there earlier it is the location where cached content is kept, this place was kept on a GADisk config file earlier but now it is sent by Bassa (ie: <cache_url>http://cache.mydomain.com/debian.iso</cache_url>). Now it is time to change GADisk database and the code according to these changes. I think we need some more fields in downloads table to keep the above mentioned additional data. Apart from that we have to add a new table called meta_content and it should have a one to many relation with downloads table (one download can have many meta content). Both XML docs have common tags, <filename>,<origin_url>,<cached_url> corresponding fields in the data base can be used to build the relationship. I would like to have a quick response. Thanks in advance. On 7/11/07, bas...@li... < bas...@li...> wrote: > > has to create a new table for bassa updates and information regarding > local url and preview clips url downloaded size, delete request etc. > > On 7/11/07, bas...@li... < > bas...@li...> wrote: > > > Gowri please let us know what changes are needed for the database? > > > > -- > > wathsala > > http://wathsalav.blogspot.com > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Bassa-devs mailing list > > Bas...@li... > > https://lists.sourceforge.net/lists/listinfo/bassa-devs > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bassa-devs mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bassa-devs > > -- wathsala http://wathsalav.blogspot.com |
|
From: <bas...@li...> - 2007-07-11 08:54:11
|
has to create a new table for bassa updates and information regarding local url and preview clips url downloaded size, delete request etc. On 7/11/07, bas...@li... < bas...@li...> wrote: > > Gowri please let us know what changes are needed for the database? > > -- > wathsala > http://wathsalav.blogspot.com > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bassa-devs mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bassa-devs > > |
|
From: <bas...@li...> - 2007-07-11 07:26:08
|
Gowri please let us know what changes are needed for the database? -- wathsala http://wathsalav.blogspot.com |
|
From: <bas...@li...> - 2007-07-09 08:33:37
|
-- wathsala http://wathsalav.blogspot.com |
