Well said Martin,

If we don't need clustered, load balanced remote objects then J2EE is
overkill, spring would be better and it runs in any J2EE container. I don't
know much of anything about FCS but once we get some requirements down we
can come up with interfaces and worry about language later.  I also do a lot
of UML, use cases, domain models, seq diagrams, I use the iconix process
which is a reduced rational approach so if once we start getting
requirements I can help organize that stuff so we can break development into
logical modular pieces.

I may need a braindump of FCS from someone sometime (john) so we can do that
on the phone sometime if the projects gets rolling.  I do have 3 projects
right now as well as a full time job (we just got another adult swim show so
I have to get our damn website updated :) )  but I should be able to put in
some decent amount of work.

Cheers,
Grant

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Martin Wood
Sent: Tuesday, August 30, 2005 9:05 PM
To: Open Source Flash Mailing List
Subject: Re: [osflash] New Flash Comm Open source project - line starts here

I think you mean JBoss and/or Spring, theres some fire out there on the 
internet when you search for the two together ;)

Anyway, im willing to chip in with what i can, i spend a lot of time 
doing back end java work (with spring :), but would like to see the 
effort being as language / platform neutral as possible.

Obviously it will head towards where the expertise lies, but I think it 
would be useful to provide a 'reference implementation' in whatever 
language, but architected to make it easily portable.

Sounds like youre a good architecture man Grant. :)

I guess the major architectural issues of the component parts of FCS 
will have been dealt with to a large degree, so looking at existing 
architectures and implementations for inspirations may be a good start.

Really, the work on reverse engineering the protocol could be done in 
parallel with the design of the system itself. We know *what* the system 
should do, just not exactly how it talks to the player.

like i said, i'll offer what i can, ideas, research, design, code etc.

martin


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to