List Info

Thread: CeltiXFire




CeltiXFire
user name
2006-09-05 09:12:11
 
Hi Richard,
 
Personally, I think you should think about moving to the new transport APIs sonner rather than later, as this is where future development effort will the concentrated.
 
It may be a bit premature to jump in right now though, as obviously we haven't got CeltiXfire at feature parity with Celtix yet.
 
However, within the next few weeks we aim to be approaching that goal.
 
Regards,
Eoghan 


From: Shaw, Richard A [mailto:richard.shawatkinsglobal.com]
Sent: 05 September 2006 08:48
To: celtixobjectweb.org
Subject: [celtix] CeltiXFire

I see there is now some code in the celtixfire repository.

I am just in the process of creating custom transports and bindings for Celtix and was wondering what the considered advice would be on whether to continue what I am doing or look at doing it with Celtixfire instead.

I'm worried about teaching my team something new now, and whether it is stable enough to use yet. But on the other hand I'm worried about wasting time on code that cannot be reused when we eventually shift to celtixfire (a quick look a the http transport source code looks a lot different).



Richard Shaw

¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤

Richard Shaw  
Technical Design Authority - Information Solutions Consultancy  
Intelligent Transport Systems

Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW

Tel: +44 (0) 1372 756407 
Fax: +44 (0) 1372 740055
Mob: 07740 817586 
E-mail: richard.shawatkinsglobal.com

www.atkinsglobal.com/its



This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )