Feature Proposals » Mdrepo to switch from Berkeley DB to Sereal
Summary
| Current State: | Developer: | Reason: | Date: | Concerns By: | Bug Tracking: | Proposed For: |
|---|---|---|---|---|---|---|
| AcceptedProposal | HideyoImazu | AcceptedByReleaseMeeting | 2017-06-02 | KampalaRelease |
Detail
| TopicSummary: | Mdrepo to switch from Berkeley DB to Sereal |
| CurrentState: | AcceptedProposal |
| CommittedDeveloper: | HideyoImazu |
| ReasonForDecision: | AcceptedByReleaseMeeting |
| DateOfCommitment: | 2017-06-02 |
| ConcernRaisedBy: | |
| BugTracking: | |
| OutstandingIssues: | |
| RelatedTopics: | |
| InterestedParties: | |
| ProposedFor: | KampalaRelease |
| TWikiContributors: |
Edit Form
Motivation
Mdrepo has been using Berkeley DB but it's architecture dependent and it doesn't work soundly when multiple servers accessing files on NFS. Writing and reading serialized data with Sereal::Encode and Sereal::Decode should be better.Description and Documentation
Re-implement TWiki::Mdrepo using Sereal and write a tool to convert Berkeley DB file to Sereal.Examples
Impact
Implementation
-- Contributors:
Hideyo Imazu - 2017-06-01
Discussion
| ChangeProposalForm | |
|---|---|
| TopicClassification | FeatureRequest |
| TopicSummary | Mdrepo to switch from Berkeley DB to Sereal |
| CurrentState | AcceptedProposal |
| CommittedDeveloper | HideyoImazu |
| ReasonForDecision | AcceptedByReleaseMeeting |
| DateOfCommitment | 2017-06-02 |
| ConcernRaisedBy | |
| BugTracking | |
| OutstandingIssues | |
| RelatedTopics | |
| InterestedParties | |
| ProposedFor | KampalaRelease |
| TWikiContributors | |
Topic revision: r3 - 2019-08-29 - HideyoImazu
Site map
Blog web
Create New Topic
Index
Search
Advanced search
My topics of interest
Changes
Major changes only
All tags
Notifications
RSS Feed
Statistics
Preferences
Community 
Readme first
Developers News
How you can help
Community roles
#twiki IRC
Lima Release
Feature Proposals
Bugs Changes
Categories 
Account 
Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.Copyright © 1999-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.