I don't get what it would be confusing with? There would still be
only only maven project called teiid. Many other OSS projects are
On Jul 14, 2009, at 4:44 PM, Ramesh Reddy wrote:
Just "Teiid" for kit would be just fine with me.
There is also a project called "teiid-embedded" which we were thinking
about changing to the same name, but calling it "teiid" also may cause
confusion, I would rather call the project "teiid-runtime" and call
On Tue, 2009-07-14 at 15:29 -0500, John Verhaeg wrote:
> Why not just "teiid"? Leave it to the peripherals to be qualified.
> On Jul 14, 2009, at 2:22 PM, John Doyle wrote:
>> I like teiid-runtime. teiid-engine occurred to me, but I think
>> runtime is better.
>> ----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
>>> As part of 6.2 release Teiid is will be providing a "Server" kit
>>> community. A initial version of this kit is available now!
>>> The build scripts are modified such that current "embedded" kit
>>> be used in multi-purpose mode, where it can support either
>>> mode or standalone server mode.
>>> The way user invokes the environment defines how the run time is
>>> 1) If user specifies embedded URL on the connection string, the
>>> runtime is loaded into host JVM, and user has Teiid Embedded
>>> 2) If server is manually started, and then if user uses the Server
>>> specific URL as the connection string, the client program can
>>> Teiid Server instance over the socket.
>>> Startup scripts for running the server are provided in the "bin"
>>> This kit is still under progress and you can monitor it under
. Try it out, give us
>>> Now, that we have single kit for both Embedded and Server, it is
>>> confusing to call it "embedded" kit. So, we need to re-name this
>>> something else. Teiid leads would like call this just
>>> but are open for other suggestions. So, if you have other
>>> for name let's hear um?
>>> teiid-dev mailing list
>> teiid-dev mailing list