You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Davanum Srinivas <da...@gmail.com> on 2005/07/05 17:43:48 UTC

Trifork

FYI, http://www.trifork.com/topmenu/news_events/release_04_07_05/

-- dims

-- 
Davanum Srinivas -http://blogs.cocoondev.org/dims/

Re: Trifork

Posted by Jacek Laskowski <jl...@apache.org>.
Jeremy Boynes wrote:

> Hopefully my comment about defining interfaces during web unification 
> and allowing alternate implementations makes a little more sense now. 

It always did ;) Since we actually know nothing about their runtime 
stack, it's hard to tell if the interface definition would be 
appropriate for them even if Tomcat and Jetty worked fine.

> They are not alone here.

I wish they were not.

> It would be good to hear from the TriFork folk on whether the LCD we are 
> working on now is adequate or whether long term they would want 
> container specific features to expose the things that make them 
> "high-performance."

I think we'll see their contribution happen in higher volume in coming days.

> Jeremy

Jacek



Re: Trifork

Posted by Jeremy Boynes <jb...@apache.org>.
Jacek Laskowski wrote:
> And I do like this:
> 
> "Trifork's next-generation application server, Trifork 5.0, will be 
> based on the Geronimo foundation while utilizing Trifork's high- 
> performance EJB and WEB containers, as well as Trifork's proven CORBA 
> implementation. Trifork will continue to support previous versions of 
> the application server, the J2EE 1.3 compatible Trifork EAS and the J2EE 
> 1.4 compatible Trifork T4."
> 
> , which points towards our discussion about simplifying web runtime. If 
> they use yet other EJB and WEB containers, we'll have to settle down on 
> what the unified system will finally look like - we can't only think 
> about Tomcat and Jetty anymore. 

Hopefully my comment about defining interfaces during web unification 
and allowing alternate implementations makes a little more sense now. 
They are not alone here.

It would be good to hear from the TriFork folk on whether the LCD we are 
working on now is adequate or whether long term they would want 
container specific features to expose the things that make them 
"high-performance."

--
Jeremy

Re: Trifork

Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Jul 6, 2005, at 2:08 AM, Joern Larsen wrote:

> Dear Alan
>
> It is true that we have mentioned four month in our announcement.  
> However you should see this as the fastest we can do the transition  
> of our code and not a timeline for the Geronimo project. By the way  
> I did not know there were a Geronimo PR team! Who are they and how  
> do I get in touch with them?
>

prc@apache.org

> We did not want to drag this announcement because we wanted our  
> customers to know where they have us. Also Geir told me that shared  
> announcements with Apache was not likely to happen. I hope no harm  
> is done!

No harm done.  For something like this, it doesn't warrant a press  
release from the ASF.

geir

-- 
Geir Magnusson Jr                                  +1-203-665-6437
geirm@apache.org



Re: Trifork

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Joern,

I'm happy to see such a highly motivated vendor joining the team!  No 
harm done.


Regards,
Alan

Joern Larsen wrote, On 7/5/2005 11:08 PM:

> Dear Alan
>
> It is true that we have mentioned four month in our announcement. 
> However you should see this as the fastest we can do the transition of 
> our code and not a timeline for the Geronimo project. By the way I did 
> not know there were a Geronimo PR team! Who are they and how do I get 
> in touch with them?
>
> We did not want to drag this announcement because we wanted our 
> customers to know where they have us. Also Geir told me that shared 
> announcements with Apache was not likely to happen. I hope no harm is 
> done!
>
> Best regards
>
> Joern
>
> Alan D. Cabrera wrote:
>
>> On 7/5/2005 2:55 PM, Jacek Laskowski wrote:
>>
>>> Davanum Srinivas wrote:
>>>
>>>> FYI, http://www.trifork.com/topmenu/news_events/release_04_07_05/
>>>
>>>
>>>
>>>
>>> Not that I'm against such announcements, but I don't understand this:
>>>
>>> "As a first step, Trifork has donated its CORBA implementation to 
>>> the project. Geronimo's transition to be using Trifork's CORBA 
>>> technology is expected to be able to complete in a less than four 
>>> months."
>>>
>>> Did they already do that? We're talking about it or am I possibly 
>>> missing something?
>>
>>
>>
>> The discussion of the exact mechanics of this work will start to 
>> trickle in to this list.  As for the four months estimate, I wish 
>> that their PR firm would have contacted Apache's PR contact before 
>> announcing time lines.
>>
>>
>>
>> Regards,
>> Alan
>>
>>
>>
>



Re: Trifork

Posted by Jacek Laskowski <jl...@apache.org>.
Joern Larsen wrote:

> However you should see this as the fastest we can do the transition of 
> our code and not a timeline for the Geronimo project.

Well, that's not written this way. I'm glad we're targetting the 
transition so early, but doubt if it really happens given we're just 
starting our development together.

> By the way I did 
> not know there were a Geronimo PR team! Who are they and how do I get in 
> touch with them?

There's no Geronimo PR, but Apache PR. I'm sure Geir would know how to 
contact them. They surely would have approached Geronimo PMC and the 
estimate wouldn't have been such an surprise. Anyway, what's said is 
said. Let's then play the game.

> Joern

Jacek


Re: Trifork

Posted by Joern Larsen <jl...@trifork.com>.
Dear Alan

It is true that we have mentioned four month in our announcement. 
However you should see this as the fastest we can do the transition of 
our code and not a timeline for the Geronimo project. By the way I did 
not know there were a Geronimo PR team! Who are they and how do I get in 
touch with them?

We did not want to drag this announcement because we wanted our 
customers to know where they have us. Also Geir told me that shared 
announcements with Apache was not likely to happen. I hope no harm is done!

Best regards

Joern

Alan D. Cabrera wrote:

> On 7/5/2005 2:55 PM, Jacek Laskowski wrote:
>
>> Davanum Srinivas wrote:
>>
>>> FYI, http://www.trifork.com/topmenu/news_events/release_04_07_05/
>>
>>
>>
>> Not that I'm against such announcements, but I don't understand this:
>>
>> "As a first step, Trifork has donated its CORBA implementation to the 
>> project. Geronimo's transition to be using Trifork's CORBA technology 
>> is expected to be able to complete in a less than four months."
>>
>> Did they already do that? We're talking about it or am I possibly 
>> missing something?
>
>
> The discussion of the exact mechanics of this work will start to 
> trickle in to this list.  As for the four months estimate, I wish that 
> their PR firm would have contacted Apache's PR contact before 
> announcing time lines.
>
>
>
> Regards,
> Alan
>
>
>

-- 

-- 
-- 
Joern Larsen
CEO

                 WHO'S AT JAOO? - http://www.jaoo.dk
-----------------------------------------------------------------------
EOS Trifork, Margrethepladsen 3, 8000  Ã…rhus C, Denmark
Tel: +45 8732 8787 / Fax: +45 8732 8788 / Mob: +45 4072 8483



Re: Trifork

Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Jul 5, 2005, at 6:30 PM, Alan D. Cabrera wrote:

> On 7/5/2005 2:55 PM, Jacek Laskowski wrote:
>
>
>> Davanum Srinivas wrote:
>>
>>
>>> FYI, http://www.trifork.com/topmenu/news_events/release_04_07_05/
>>>
>>
>>
>> Not that I'm against such announcements, but I don't understand this:
>>
>> "As a first step, Trifork has donated its CORBA implementation to  
>> the project. Geronimo's transition to be using Trifork's CORBA  
>> technology is expected to be able to complete in a less than four  
>> months."
>>
>> Did they already do that? We're talking about it or am I possibly  
>> missing something?
>>
>
> The discussion of the exact mechanics of this work will start to  
> trickle in to this list.  As for the four months estimate, I wish  
> that their PR firm would have contacted Apache's PR contact before  
> announcing time lines.

No one here discussed those dates, so chalk it up to aggressive PR.   
However, if they do think they can help get that done in 4 months,  
that's cool... :)

geir


>
>
>
> Regards,
> Alan
>
>
>
>

-- 
Geir Magnusson Jr                                  +1-203-665-6437
geirm@apache.org



Re: Trifork

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On 7/5/2005 2:55 PM, Jacek Laskowski wrote:

> Davanum Srinivas wrote:
>
>> FYI, http://www.trifork.com/topmenu/news_events/release_04_07_05/
>
>
> Not that I'm against such announcements, but I don't understand this:
>
> "As a first step, Trifork has donated its CORBA implementation to the 
> project. Geronimo's transition to be using Trifork's CORBA technology 
> is expected to be able to complete in a less than four months."
>
> Did they already do that? We're talking about it or am I possibly 
> missing something?

The discussion of the exact mechanics of this work will start to trickle 
in to this list.  As for the four months estimate, I wish that their PR 
firm would have contacted Apache's PR contact before announcing time lines.



Regards,
Alan




Re: Trifork

Posted by Jacek Laskowski <jl...@apache.org>.
Davanum Srinivas wrote:
> FYI, http://www.trifork.com/topmenu/news_events/release_04_07_05/

Not that I'm against such announcements, but I don't understand this:

"As a first step, Trifork has donated its CORBA implementation to the 
project. Geronimo's transition to be using Trifork's CORBA technology is 
expected to be able to complete in a less than four months."

Did they already do that? We're talking about it or am I possibly 
missing something?

And I do like this:

"Trifork's next-generation application server, Trifork 5.0, will be 
based on the Geronimo foundation while utilizing Trifork's high- 
performance EJB and WEB containers, as well as Trifork's proven CORBA 
implementation. Trifork will continue to support previous versions of 
the application server, the J2EE 1.3 compatible Trifork EAS and the J2EE 
1.4 compatible Trifork T4."

, which points towards our discussion about simplifying web runtime. If 
they use yet other EJB and WEB containers, we'll have to settle down on 
what the unified system will finally look like - we can't only think 
about Tomcat and Jetty anymore. I also wonder how easy is to embbed 
another EJB container. Great times are coming...

> -- dims

Jacek