I like teiid-runtime. teiid-engine occurred to me, but I think runtime is better. ~jd ----- "Ramesh Reddy" <rareddy(a)redhat.com&gt; wrote: > As part of 6.2 release Teiid is will be providing a "Server" kit for > community. A initial version of this kit is available now! > > The build scripts are modified such that current "embedded" kit can > now > be used in multi-purpose mode, where it can support either "embedded" > mode or standalone server mode. > > The way user invokes the environment defines how the run time is > started. > > 1) If user specifies embedded URL on the connection string, the Teiid > 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 connect > to > Teiid Server instance over the socket. > > Startup scripts for running the server are provided in the "bin" > folder. > This kit is still under progress and you can monitor it under > https://jira.jboss.org/jira/browse/TEIID-259. Try it out, give us > your > feedback. > > 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 kit > to > something else. Teiid leads would like call this just > "teiid-runtime", > but are open for other suggestions. So, if you have other suggestions > for name let's hear um? > > Thanks > > Ramesh.. > > > _______________________________________________ > teiid-dev mailing list > teiid-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/teiid-dev _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev

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 the kit "teiid" Ramesh.. 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. >> >> ~jd >> >> ----- "Ramesh Reddy" <rareddy(a)redhat.com&gt; wrote: >> >>> As part of 6.2 release Teiid is will be providing a "Server" kit >>> for >>> community. A initial version of this kit is available now! >>> >>> The build scripts are modified such that current "embedded" kit can >>> now >>> be used in multi-purpose mode, where it can support either >>> "embedded" >>> mode or standalone server mode. >>> >>> The way user invokes the environment defines how the run time is >>> started. >>> >>> 1) If user specifies embedded URL on the connection string, the >>> Teiid >>> 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 >>> connect >>> to >>> Teiid Server instance over the socket. >>> >>> Startup scripts for running the server are provided in the "bin" >>> folder. >>> This kit is still under progress and you can monitor it under >>> https://jira.jboss.org/jira/browse/TEIID-259. Try it out, give us >>> your >>> feedback. >>> >>> 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 >>> kit >>> to >>> something else. Teiid leads would like call this just >>> "teiid-runtime", >>> but are open for other suggestions. So, if you have other >>> suggestions >>> for name let's hear um? >>> >>> Thanks >>> >>> Ramesh.. >>> >>> >>> _______________________________________________ >>> teiid-dev mailing list >>> teiid-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/teiid-dev >> _______________________________________________ >> teiid-dev mailing list >> teiid-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/teiid-dev > > Thanks, > > JPAV > > >

If you consider all the projects together under the name Teiid, then there would another sub-project called Teiid. During a conversation if I want to mention this to someone I can say go to Teiid:Teiid project and look at Foo class. I can not agree that is not confusing. Ramesh.. On Tue, 2009-07-14 at 16:50 -0500, John Verhaeg wrote: > 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 > organized similarly. > > 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 > > the > > kit "teiid" > > > > Ramesh.. > > > > 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. > >>> > >>> ~jd > >>> > >>> ----- "Ramesh Reddy" <rareddy(a)redhat.com&gt; wrote: > >>> > >>>> As part of 6.2 release Teiid is will be providing a "Server" kit > >>>> for > >>>> community. A initial version of this kit is available now! > >>>> > >>>> The build scripts are modified such that current "embedded" kit can > >>>> now > >>>> be used in multi-purpose mode, where it can support either > >>>> "embedded" > >>>> mode or standalone server mode. > >>>> > >>>> The way user invokes the environment defines how the run time is > >>>> started. > >>>> > >>>> 1) If user specifies embedded URL on the connection string, the > >>>> Teiid > >>>> 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 > >>>> connect > >>>> to > >>>> Teiid Server instance over the socket. > >>>> > >>>> Startup scripts for running the server are provided in the "bin" > >>>> folder. > >>>> This kit is still under progress and you can monitor it under > >>>> https://jira.jboss.org/jira/browse/TEIID-259. Try it out, give us > >>>> your > >>>> feedback. > >>>> > >>>> 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 > >>>> kit > >>>> to > >>>> something else. Teiid leads would like call this just > >>>> "teiid-runtime", > >>>> but are open for other suggestions. So, if you have other > >>>> suggestions > >>>> for name let's hear um? > >>>> > >>>> Thanks > >>>> > >>>> Ramesh.. > >>>> > >>>> > >>>> _______________________________________________ > >>>> teiid-dev mailing list > >>>> teiid-dev(a)lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/teiid-dev > >>> _______________________________________________ > >>> teiid-dev mailing list > >>> teiid-dev(a)lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/teiid-dev > >> > >> Thanks, > >> > >> JPAV > >> > >> > >> > > > > Thanks, > > JPAV > > > _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev