As a follow-up to our recent proposal document, we plan to release a parallel, patched version of Gears containing the proposed module. In order to minimize the code conflicts between the versions, we plan on creating a separate project that maintains a single patch file. To build the patched version from source, a user would first get the latest code from http://gears.googlecode.com/svn/trunk/, and then apply the patch file. The planned name for this project is “UltraLiteWeb Patch for Gears”.
In addition to providing a source patch, we also plan on supplying precompiled binaries. In the same way that Google creates and hosts binary builds of the Gears project, we will also create and host Sybase builds (that contain the patch). However, to avoid confusion with the Google builds, the Sybase builds will use “UltraLiteWeb” as the product short name. I would also like to use the following derivative icon: http://iablog.sybase.com/efarrar/wp-content/uploads/2009/08/icon_48x48.png to make it clear that this is simply a patched version of Gears. Please let me know if you have any concerns about the course we are taking towards releasing a patched version. I would be happy to provide this group with the patch code and/or binaries before making them public if you would like to do some compatibility testing first. Thanks, Eric Farrar On Jul 28, 2:24 pm, Eric Farrar <[email protected]> wrote: > Over the past few months I have been working on firming up some > prototyping work that was discussed on this forum several months ago > (http://groups.google.com/group/gears-eng/browse_thread/thread/1f643be... > ). In brief, I am working on implementing a module to enable secure, > relational synchronization between a MobiLink server, and an UltraLite > relational database running in the browser. > > Since I would eventually like to see this module embraced by the broad > Gears project, I would like to solicit some early feedback on the API. > However, I do recognize some aspects of the proposed module may make > it unsuitable for broad adoption in the short term. If that is the > case, we may still pursue releasing a parallel ‘patched’ distribution > of Gears that contains this module (as discussed in the previous > conversations). > > In response to the request that we work with the Gears team to ensure > that, “the two versions don’t clobber each other in the wild,” I have > prepared a formal API proposal document. I am currently hosting that > document on my blog > athttp://iablog.sybase.com/efarrar/wp-content/uploads/2009/07/uldatabas... > . While I am hosting the document at the moment, I would like to add > it to the official Gears wiki alongside the other API proposal > documents. > > The purpose of the document is to outline the purpose and APIs of the > proposed ULDatabase module. Since I want to conform to the ‘feel’ of > the other Gear’s modules, I am welcoming any comments or criticisms on > this API, or on the idea as a whole. > > I should mention that this document only discusses the APIs of the > proposed module, and does not address the complications of the > coexistence of a parallel distribution. That said, we have spent a > good deal of time looking into the complications of coexistence (using > the feedback from the previous conversation), and are confident that > we have a working solution. We can discuss the coexistence issues in > more detail if it turns out we need to go that route. > > Thanks in advance, > > Eric Farrar
