Hi All Tapestry Ppl,
IoC caught my eye when I first touched tapestry some years back and I've
been fortunate to have a good dig at tapestry for web development a few
times this year again!
I'd like to use Tapestry-IoC in my old-pet open source project for
controlling older telecommunications equipment, Open CSTA Server.
Specifically,
1. Server is multi-threaded, does not run in servlet API.
2. One thread per connected raw TCP client (interface TCPOwnerInterface),
potentially adding HTTP/XMMP/SIP client/server implementations
3. One "Link" whether Serial connection or Network connection to
equipment (interface CSTA_Link_Interface <- how i learned a bit of generic
programming)
1,2,3 all seem within the realm of Tapestry-IoC's uses.
aaa) What are the basics in firing it up? Say from a main() method,
*unmanaged* i know...i read the IoC overview :)
I also used to have a development philosophy that everything should be
Runnable so it was easier to throw into an executor thread pool for
testing stuff quickly (with equipment responses, not mock testing) and
hackily.
The project opencsta project source code is ready for a code update and
I'd like to start using Tapestry-IoC to learn better ways of doing stuff...
I think getting question [aaa] answered will keep me busy finding time for
the rest of the month tinkering with it if someone could suggest a quick
and easy first step.
Thanks for reading,
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
