Requesting feedback on new module proposal: ULDatabase
1 view
Skip to first unread message
Eric Farrar
Jul 28, 2009, 2:24:37 PM7/28/09
to Gears Engineering Team, eric....@ianywhere.com
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/1f643beb7265c842/80555a275f9f3409#80555a275f9f3409
). 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 at http://iablog.sybase.com/efarrar/wp-content/uploads/2009/07/uldatabase_proposal.html
. 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
prototyping work that was discussed on this forum several months ago
( http://groups.google.com/group/gears-eng/browse_thread/thread/1f643beb7265c842/80555a275f9f3409#80555a275f9f3409
). 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 at http://iablog.sybase.com/efarrar/wp-content/uploads/2009/07/uldatabase_proposal.html
. 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
Eric Farrar
Aug 12, 2009, 2:37:09 PM8/12/09
to Gears Engineering Team
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 <ianywhere.efar...@gmail.com> 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...
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 <ianywhere.efar...@gmail.com> 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
> ). 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...
> 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
Eric Farrar
Sep 1, 2009, 10:59:36 AM9/1/09
to Gears Engineering Team
Does anyone in this group have concerns about using the proposed icon
( http://iablog.sybase.com/efarrar/wp-content/uploads/2009/08/icon_48x48.png
) for the patch outlined in the previous posts?
Thanks,
Eric Farrar
On Aug 12, 2:37 pm, Eric Farrar <ianywhere.efar...@gmail.com> wrote:
> 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 fromhttp://gears.googlecode.com/svn/trunk/, and then
( http://iablog.sybase.com/efarrar/wp-content/uploads/2009/08/icon_48x48.png
) for the patch outlined in the previous posts?
Thanks,
Eric Farrar
On Aug 12, 2:37 pm, Eric Farrar <ianywhere.efar...@gmail.com> wrote:
> 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
> 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_48x4...
> “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.
>
erfa...@gmail.com
Sep 1, 2009, 10:51:47 AM9/1/09
to Gears Engineering Team
Does anyone in this group have concerns about using the proposed icon
( http://iablog.sybase.com/efarrar/wp-content/uploads/2009/08/icon_48x48.png
) for the project outlined in the previous posts?
( http://iablog.sybase.com/efarrar/wp-content/uploads/2009/08/icon_48x48.png
Thanks,
On Aug 12, 2:37 pm, Eric Farrar <ianywhere.efar...@gmail.com> wrote:
> 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
> 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_48x4...
> “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.
>
Nigel Tao
Sep 3, 2009, 3:56:06 AM9/3/09
to Gears Engineering Team
On Sep 2, 12:51 am, "erfar...@gmail.com" <erfar...@gmail.com> wrote:
> Does anyone in this group have concerns about using the proposed icon
> (http://iablog.sybase.com/efarrar/wp-content/uploads/2009/08/icon_48x4...
> Does anyone in this group have concerns about using the proposed icon
> ) for the project outlined in the previous posts?
I am not a lawyer, and I'm not speaking for Google, but if it matters,
I personally don't have a concern about your proposed icon.
Reply all
Reply to author
Forward
0 new messages