[osflash] Remoting for .NET - proposal and request for advice

[Paul Robertson]

Well, I've looked around and haven't found one of these, but it would be 
helpful for me, so I'm proposing a new OS Flash project: An open-source 
Flash Remoting gateway for .NET

Since the kind folks who built AMFPHP have already done so much of the work, 
I was thinking of using that implementation as the jumping-off point, in 
particular for the deserialization/serialization, but also for the 
architecture unless I can find reasons not to.

Any thoughts? I'm sure there are several people on this list with plenty of 
AMFPHP experience. I don't know if Patrick Mineault is on this list, but if 
you are (or others who have been involved in designing/building AMFPHP) then 
I would greatly appreciate your insights. For my part I have used AMFPHP 
somewhat (I have php on my personal site; .NET at work) and have dug into 
the source code quite a bit in anticipation of this project.

Here are some questions I have, that I would love to get feedback on:

- What are some of the strengths and weaknesses of the AMFPHP architecture? 
If you could design that system from scratch today, would you use the same 
architecture or a different one?

- Anyone else attempted to build an AMF gateway? What lessons did you learn? 
Should I turn back now while I'm ahead? =)

- Is anyone else interested in having (or helping build or test) an OS Flash 
Remoting gateway for .NET?

Obviously there will be some necessary changes due to differences in PHP and 
C#/.NET, and I already have some thoughts about some changes based on 
specific things that are available in .NET that (I assume) aren't available 
in PHP. But having never designed an AMF gateway before, I'd appreciate 
thoughts from any of you who have done so, or at least spent some time 
thinking about it.

Thanks for your feedback!

Paul Robertson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/osflash_osflash.org/attachments/20050912/5e51de38/attachment.htm