Very interesting subject Paul. I for one will be trying it out if something like this gets as far as it could. I didn't search for alternatives, and am holding back on non-open sourced projects. I have 0 experience with remoting, because it was always such a haslle for me to implement it in my c# projects. I always found that using xml was more understandable and adjustable for me. That's why i build my own 'remoting' using xml packets. I did however understand the advantages which pure remoting can have and have always been on the lookout for any promising projects. Long story short, good initiative if you choose to carry it on. If i have a feeling i can add something usefull i will. Knowledge of amf and remoting in general is too slim to help you out in the beginning though. P.S. Porting java code to c# is peanuts if it doesn't use too many external libraries. The coding is 90% the same in my "low level java port" projects. So the openamf might seem to be the easier starting point. Grt, Ben Smeets
________________________________
From: [EMAIL PROTECTED] on behalf of Paul Robertson
Sent: Mon 9/12/2005 11:17 PM
To: Open Source Flash Mailing List
Subject: Re: [osflash] Remoting for .NET - proposal and request for advice
Not *too* unfortunate -- it saves me the trouble of having to write it =)
The download I found includes the .Net assembly, but no source code (or
documentation for that matter) that I could find. (If someone else found more,
please let me know so I can get my glasses checked =)
So if there is interest among others even in light of the existince of the
starwolf implementation, then I think there could be a reason to build it
still. After all, as was mentioned, FlashORB has a lot of nice features, and it
can even be used for free under certain circumstances, but
Don't get me wrong, I'm not one to build something just for the sake of
building it (well, maybe sometimes, but not with my current schedule...). And
since just today I read your (Patrick's) blog post about small open source
projects not being sustainable, I am trying to keep a healthy amount of
skepticism before diving into something like this.
In any case, Patrick in particular or anyone else with some experience with
this, if you have a little time sometime soon I would be very interested in
hearing from you about the architecture of AMFPHP and whether you would build
it the same way if you were starting from scratch. I think since (if I read
things correctly) you weren't the original lead developer you could provide
some interesting insights in that regard.
Maybe a future blog entry? I for one am one of your readers =)
Anyway, I appreciate the interest and thoughts that have been expressed so far,
and am still interested in thoughts that others may have about the architecture
of an AMF gateway, just in case...
Paul
On 9/12/05, Patrick Mineault <[EMAIL PROTECTED]> wrote:
Yes I'm on the list, and unfortunately for you you've been beat already.
There is an (early) implementation of Remoting for .NET, it's on
starwolf.ch.
Patrick Mineault
Thompson, Daniel wrote:
>Paul
>
>You may want to check out OpenAMF [http://www.openamf.org/], an
open-source Java remoting gateway.
>Architectural considerations are much more similar between Java and
.NET than PHP and .NET, so it may
>be a better version to port (assuming they've already solved those
problems).
>
>-dt
>
>-----Original Message-----
>
>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
>
>
>_______________________________________________
>osflash mailing list
>[email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
<http://osflash.org/mailman/listinfo/osflash_osflash.org>
>
>
>
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
<<winmail.dat>>
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
