From chippersbox at gmail.com Wed Aug 1 09:13:54 2007 From: chippersbox at gmail.com (Christian) Date: Wed, 1 Aug 2007 23:13:54 +1000 Subject: [Rubyamf-discussion] Amf Rest Message-ID: <3f6943fa0708010613l53cad36dj378bf2d53fc6822a@mail.gmail.com> Hi, I'm new to rubyamf, and fairly new to ruby and rails so please forgive me if any of my terminology is not quite right. I've been playing with rubyamf and came across an error when trying to call redirect_to in the rubyamf_controller when the content type is not x-amf. The error I received was this: ArgumentError (wrong number of arguments (0 for 1)): c:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1096:in `render' c:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1096:in `perform_action_without_filters' ... etc... I've traced the problem to be the redefinition of the render method in rubyamf_core/util/action_controller_run_target.rb. The problem only comes up once the rubyamf controller has been called, which makes perfect sense as before then, the standard render method is being used, and not the rubyamf one. At first I thought it might have been my setup, and normally once a controller has been called, it 'magically' undoes any changes to classes (Such as ActionController::Base) that have been made, but for my mind that seems pretty much impossible as it is a ruby thing overriding the method, not a rails thing, if that make sense. As I don't intend to use REST like logic in this application, I have simply commented out the redefinition and all is well again, but as some people may want to use this, I thought I could offer up a couple of solutions that might work. 1. Instead of redefining methods in the Base class, extend it. This would then mean that any controller wanting to use anything like amf_credentials for example, would need to have there controller extend this class instead of ActionController::Base. This still might cause issues if something like a render :file was called from that controller. I'm really not too sure. It could be very easily worked around by implementing the function as such though: def render(options = nil, deprecated_status = nil, &block) if (!options.nil? && options[:amf]) self.used_render_amf = true self.amf_content = hash[:amf] else super(options, deprecated_status, &block) end end I'm not sure if that would work, as I am new to ruby. I know in languages such as java the super call needs to be the first call made in the function. Option 2. This goes against the DRY principle, but simply copy the entire render method from actionpack, and simply add amf to be one of the options. Similar issues may be had with the respond_to method, but I haven't had any as yet. Hope this was helpful. Have a great day. Christian -- "Every child has many wishes. Some include a wallet, two chicks and a cigar, but that's another story." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070801/3da7795d/attachment.html From mrussell at inpses.co.uk Wed Aug 1 09:24:20 2007 From: mrussell at inpses.co.uk (Max Russell) Date: Wed, 1 Aug 2007 14:24:20 +0100 Subject: [Rubyamf-discussion] Automating Flex with Ruby-AMF Message-ID: Has anyone had any experience with using RubyAMF for testing swfs? Is this even possible? Regards Max Max Russell Senior Test Analyst INPS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070801/334f6b67/attachment.html From beingthexemplary at gmail.com Wed Aug 1 10:21:38 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Wed, 1 Aug 2007 10:21:38 -0400 Subject: [Rubyamf-discussion] Automating Flex with Ruby-AMF In-Reply-To: References: Message-ID: Hey Max, I haven't heard anyone try this. What kind of workflow are you going for? Not sure what you mean by "testing" swfs.. -Aaron On 8/1/07, Max Russell wrote: > > Has anyone had any experience with using RubyAMF for testing swfs? Is > this even possible? > > > > Regards > > Max > > > > *Max Russell* > Senior Test Analyst > *INPS* > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070801/6d5080ef/attachment.html From beingthexemplary at gmail.com Wed Aug 1 10:31:28 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Wed, 1 Aug 2007 10:31:28 -0400 Subject: [Rubyamf-discussion] Amf Rest In-Reply-To: <3f6943fa0708010613l53cad36dj378bf2d53fc6822a@mail.gmail.com> References: <3f6943fa0708010613l53cad36dj378bf2d53fc6822a@mail.gmail.com> Message-ID: You shouldn't ever modify the rubyamf_controller. If you're modifying the RubyAMF controller it will cause problems. Are you putting a "redirect_to" in the rubyamf_controller.rb? You have to keep in mind that things like redirects don't apply to Flash Remoting. Actually, most things with Rails won't apply to RubyAMF just because of the nature of Flash Remoting. -Aaron On 8/1/07, Christian wrote: > > Hi, > > I'm new to rubyamf, and fairly new to ruby and rails so please forgive me > if any of my terminology is not quite right. > > I've been playing with rubyamf and came across an error when trying to > call redirect_to in the rubyamf_controller when the content type is not > x-amf. The error I received was this: > > ArgumentError (wrong number of arguments (0 for 1)): > c:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1096:in > `render' > c:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1096:in `perform_action_without_filters' > ... etc... > > I've traced the problem to be the redefinition of the render method in > rubyamf_core/util/action_controller_run_target.rb. The problem only comes up > once the rubyamf controller has been called, which makes perfect sense as > before then, the standard render method is being used, and not the rubyamf > one. > > At first I thought it might have been my setup, and normally once a > controller has been called, it 'magically' undoes any changes to classes > (Such as ActionController::Base) that have been made, but for my mind that > seems pretty much impossible as it is a ruby thing overriding the method, > not a rails thing, if that make sense. > > As I don't intend to use REST like logic in this application, I have > simply commented out the redefinition and all is well again, but as some > people may want to use this, I thought I could offer up a couple of > solutions that might work. > 1. Instead of redefining methods in the Base class, extend it. This would > then mean that any controller wanting to use anything like amf_credentials > for example, would need to have there controller extend this class instead > of ActionController::Base. This still might cause issues if something like a > render :file was called from that controller. I'm really not too sure. It > could be very easily worked around by implementing the function as such > though: > > def render(options = nil, deprecated_status = nil, &block) > if (!options.nil? && options[:amf]) > self.used_render_amf = true > self.amf_content = hash[:amf] > else > super(options, deprecated_status, &block) > end > end > > I'm not sure if that would work, as I am new to ruby. I know in languages > such as java the super call needs to be the first call made in the function. > > Option 2. This goes against the DRY principle, but simply copy the entire > render method from actionpack, and simply add amf to be one of the options. > > Similar issues may be had with the respond_to method, but I haven't had > any as yet. > > Hope this was helpful. > > Have a great day. > > Christian > > -- > > "Every child has many wishes. Some include a wallet, two chicks and a > cigar, but that's another story." > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070801/ba501790/attachment-0001.html From mrussell at inpses.co.uk Wed Aug 1 10:56:28 2007 From: mrussell at inpses.co.uk (Max Russell) Date: Wed, 1 Aug 2007 15:56:28 +0100 Subject: [Rubyamf-discussion] Automating Flex with Ruby-AMF Message-ID: Hi- We've got an application that is written in Flex (2). I've had a little play with the demo example on the RubyAMF site which deals with, really, what I'd see as the backend - e.g. serving up classes& methods to the swf object (Flash) on the page via Flash remoting. What I'm wanting to do is be able to drive the application - that is to say, simulate user interaction at the browser. I've got quite a bit of WATiR experience, having written a test harness for a legacy application, however that application used a mix of Coldfusion and AJAX and the DOM could (mostly) be got at and manipulated. However, with a swf object in the page, I can't really code along the lines of "click this button, that button, then this button". So I've been looking at the win32ole library in combination with auto-it, in order to drive the mouse to fixed positions (which is evil-nasty). If I set the hWnd to a fixed resolution & position it shouldn't be *too* nasty. So, to get back to the point, I suppose I'm asking if anyone has used RubyAMF in a more driving role. Not directly sending serialised data, but more as an emulation of user experience. Max ________________________________ From: aaron smith [mailto:beingthexemplary at gmail.com] Sent: 01 August 2007 15:22 To: Max Russell Cc: rubyamf-discussion at rubyforge.org Subject: Re: [Rubyamf-discussion] Automating Flex with Ruby-AMF Hey Max, I haven't heard anyone try this. What kind of workflow are you going for? Not sure what you mean by "testing" swfs.. -Aaron On 8/1/07, Max Russell wrote: Has anyone had any experience with using RubyAMF for testing swfs? Is this even possible? Regards Max Max Russell Senior Test Analyst INPS _______________________________________________ Rubyamf-discussion mailing list Rubyamf-discussion at rubyforge.org http://rubyforge.org/mailman/listinfo/rubyamf-discussion -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070801/42bed24b/attachment.html From beingthexemplary at gmail.com Wed Aug 1 12:43:37 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Wed, 1 Aug 2007 12:43:37 -0400 Subject: [Rubyamf-discussion] Automating Flex with Ruby-AMF In-Reply-To: References: Message-ID: Hey Max, I see what you're going for. I've been in a similar situation in the past. I previously ran into an app that claimed to be able to do automated testing on flex 2. Sorry I can't remember what the heck it was, but I'm sure it could be found. Also do a search on google for "flex 2 automated testing". There is an Adobe supported Flex 2 Automated Testing Framework. That google search should get you in the right direction to get started. As for RubyAMF and testing. RubyAMF is not at a point where you could control a SWF. I'm trying to think of options to be able to do this with RubyAMF but I think the conclusion will be to use that automated testing framework. I'll let you know if I have any break-through ideas. -Aaron On 8/1/07, Max Russell wrote: > > Hi- > > > > We've got an application that is written in Flex (2). > > I've had a little play with the demo example on the RubyAMF site which > deals with, really, what I'd see as the backend ? e.g. serving up classes& > methods to the swf object (Flash) on the page via Flash remoting. > > > > What I'm wanting to do is be able to drive the application ? that is to > say, simulate user interaction at the browser. > > > > I've got quite a bit of WATiR experience, having written a test harness > for a legacy application, however that application used a mix of Coldfusion > and AJAX and the DOM could (mostly) be got at and manipulated. > > However, with a swf object in the page, I can't really code along the > lines of "click this button, that button, then this button". > > > > So I've been looking at the win32ole library in combination with auto-it, > in order to drive the mouse to fixed positions (which is evil-nasty). If I > set the hWnd to a fixed resolution & position it shouldn't be **too** > nasty. > > > > So, to get back to the point, I suppose I'm asking if anyone has used > RubyAMF in a more driving role. Not directly sending serialised data, but > more as an emulation of user experience. > > > > Max > > > ------------------------------ > > *From:* aaron smith [mailto:beingthexemplary at gmail.com] > *Sent:* 01 August 2007 15:22 > *To:* Max Russell > *Cc:* rubyamf-discussion at rubyforge.org > *Subject:* Re: [Rubyamf-discussion] Automating Flex with Ruby-AMF > > > > Hey Max, > > I haven't heard anyone try this. What kind of workflow are you going for? > Not sure what you mean by "testing" swfs.. > > -Aaron > > > On 8/1/07, *Max Russell* wrote: > > Has anyone had any experience with using RubyAMF for testing swfs? Is this > even possible? > > > > Regards > > Max > > > > *Max Russell* > Senior Test Analyst > *INPS* > > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070801/67da9b9f/attachment.html From mrussell at inpses.co.uk Thu Aug 2 04:14:28 2007 From: mrussell at inpses.co.uk (Max Russell) Date: Thu, 2 Aug 2007 09:14:28 +0100 Subject: [Rubyamf-discussion] Automating Flex with Ruby-AMF Message-ID: Cheers anyway Aaron! I know that Mercury Quick Test Pro has support for AMF3. I don't know whether it drives it directly. We've got Borland Silk here, but were told there won't be AMF3 support for some time. Maybe it's just reinventing the wheel but I do prefer a tailored approach if possible. Thanks. Max Russell Senior Test Analyst INPS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070802/7e5087d0/attachment-0001.html From beingthexemplary at gmail.com Sun Aug 12 13:52:38 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Sun, 12 Aug 2007 13:52:38 -0400 Subject: [Rubyamf-discussion] RubyAMF + Rails, Rebuilding parts of the plugin. Message-ID: Hey All of FlexibleRails. I have some unfortunate news. I've been thinking about this for a while and decided I need to do this. I've been running into problem after problem with RubyAMF on Rails. The problems start to show up when a "real" rails application is using RubyAMF. By "real" I mean an application that wasn't a "hello world" test or simple data type tests for remoting. For example, using the authenticated plugin. When I put RubyAMF into a rails app that has more going on than just some base Rails functionality, everything just breaks. There is a lot of re-thinking I need to do in order to correct the RubyAMF on Rails plugin. As I don't want people's rails applications breaking when they want to use remoting, just because they have some plugin. Ya know? So I've talked talked to Peter about continuing on with the book, not publishing the RubyAMF chapters yet, maybe we only do them in pdf form later in the year. I really want RubyAMF to be the best ruby / rails remoting option. I don't think this is good enough to put in a book right now. Just because it doesn't play well with an advanced Rails app. I do want RubyAMF to be in the book at some point, I've already been looking into re-working RubyAMF internals for Rails. And RubyAMF is still awesome, the standalone and the rails plugin is 10% faster than WebORB for sure! But I want it to be the best and I don't think this would be a good representation. Another example problem with RubyAMF right now is when Rails is in production mode. Because I redefine the render method on an action controller. If you're trying to use remoting through RubyAMF plus an HTML web application, as soon as one remoting method is called you've lost the entire render method, no longer being able to render html / xml / whatever. That is caused because Rails locks the code at runtime, thus as soon as I redefine the render method, you're screwed. It works in development because classes are reloaded at every request. AHH, big problem. As I've been working on Pomodo for RubyAMF + Rails, I just realize more and more that in a "real" application, this is not a good fit. It needs an overhaul. I'm actually somewhat glad that I've had this chance to be working on Pomodo for RubyAMF + Rails, because it has exposed most problems that other people are probably running into, which I can fix. So I'm taking this experience as a blessing, not a mess. The API to use RubyAMF in Rails will not change, render :amf, all that is there now will work the same except the internals of the plugin will be re-written. The RubyAMF stand-alone version is stable, it's tying it in with Rails that I need to rethink. So I hope I don't disappoint too much, and I hope you understand that I want RubyAMF to be the best, and most solid option for Rails remoting, which requires me to do a bit of re-thinking and re-factoring of the Rails plugin in order to get it right. The RubyAMF internals are still stable, trust me I've done all kinds of tests with RubyAMF + Rails and all datatypes / amf functionality works fine. With exception of VO mappings which I have ready in 1.3. Now it's time to make sure it will play well with most applications it encounters. I don't think I can ever guarantee RubyAMF to work with every single plugin / Rails piece of code that is written, that's just not possible. But I can at least make it way better. I would imagine I'll have everything changed and ready in 2 months. 2 months? Don't think I'm lazy, I have other things going on. I'm moving to San Fran in two weeks! I also want to start connecting with some Flex groups in San Fran, talk some RubyAMF. So watch the blog for that, at some point I'll set up a RubyAMF group. Here's good news about 1.3 though. I'm just about done with it. Here's what it adds: - Complete VO mappings. No overhead on the RubyAMF core either. - Added a VO mappings file. - recursive_active_record_adapter. This is so that AR results with sets of other AR results on them are written to the stream as well. Currently the AR adapter only writes the top level results. This does add little overhead. - fixed a deserializer bug Of course I'll send out emails and post on the blog when it's out. Sorry for the inconvenience, take care everyone. Aaron RubyAMF -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070812/2c9a1cee/attachment.html From grimm at grimmwerks.com Fri Aug 24 20:21:38 2007 From: grimm at grimmwerks.com (grimmwerks) Date: Fri, 24 Aug 2007 20:21:38 -0400 Subject: [Rubyamf-discussion] flex and debug vs non-debug Message-ID: <60ECE47C-ABBF-40B6-95A3-8D5E452A31DF@grimmwerks.com> Hey all - my first real foray into all this so please bear with me. When I run flex in debug mode, I get a 'hello world' return; when I run it in regular mode, I get a 'send failed'. It seems the return is the 500 page. Any ideas? I can post my dev logs, i just don't want to fill the place with noise on the first post; but this is driving me nuts. From grimm at grimmwerks.com Fri Aug 24 20:54:22 2007 From: grimm at grimmwerks.com (grimmwerks) Date: Fri, 24 Aug 2007 20:54:22 -0400 Subject: [Rubyamf-discussion] flex and debug vs non-debug In-Reply-To: <60ECE47C-ABBF-40B6-95A3-8D5E452A31DF@grimmwerks.com> References: <60ECE47C-ABBF-40B6-95A3-8D5E452A31DF@grimmwerks.com> Message-ID: <8677AEF2-AA9A-4CBD-B5FA-BA8F0552B5B4@grimmwerks.com> This is totally driving me nuts: when in debug mode I get: Processing RubyamfController#gateway (for 127.0.0.1 at 2007-08-24 20:52:37) [POST] Session ID: f3cb7796bd4e6cffe6fdfcf34cc0bae7 Parameters: {"action"=>"gateway", "controller"=>"rubyamf"} SQL (0.000153) SET SQL_AUTO_IS_NULL=0 User Load (0.000256) SELECT * FROM users User Columns (0.010726) SHOW FIELDS FROM users Completed in 0.04673 (21 reqs/sec) | Rendering: 0.00011 (0%) | DB: 0.01113 (23%) | 200 OK [http://localhost/rubyamf/gateway] When in NON debug I get: > can't convert false into Integer > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:229:in `|' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:229:in `read_amf3_integer' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:202:in `read_amf3' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:423:in `read_amf3_object' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:422:in `each' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:422:in `read_amf3_object' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:214:in `read_amf3' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:149:in `read' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:489:in `read_array' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:487:in `upto' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:487:in `read_array' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:172:in `read' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:126:in `bodys' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:109:in `upto' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:109:in `bodys' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/io/ > amf_deserializer.rb:39:in `rubyamf_read' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/app/ > filters.rb:26:in `run' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/app/ > filters.rb:18:in `run' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/app/ > filters.rb:17:in `each' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/app/ > filters.rb:17:in `run' > /Users/grimm/rubyamf_rails/vendor/plugins/rubyamf/rubyamf_core/app/ > rails_gateway.rb:43:in `service' > ./script/../config/../app/controllers/rubyamf_controller.rb:72:in > `gateway' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:1095:in `send' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:1095:in `perform_action_without_filters' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/filters.rb:632:in `call_filter' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/filters.rb:619:in `perform_action_without_benchmark' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/benchmarking.rb:66:in > `perform_action_without_rescue' > /opt/local/lib/ruby/1.8/benchmark.rb:293:in `measure' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/benchmarking.rb:66:in > `perform_action_without_rescue' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/rescue.rb:83:in `perform_action' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:430:in `send' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:430:in `process_without_filters' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/filters.rb:624:in > `process_without_session_management_support' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/session_management.rb:114:in `process' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:330:in `process' > /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/dispatcher.rb: > 41:in `dispatch' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > rails.rb:78:in `process' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > rails.rb:76:in `synchronize' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > rails.rb:76:in `process' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 618:in `process_client' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 617:in `each' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 617:in `process_client' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `initialize' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `new' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 720:in `initialize' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 720:in `new' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 720:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > configurator.rb:271:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > configurator.rb:270:in `each' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > configurator.rb:270:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/mongrel_rails: > 127:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > command.rb:211:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/mongrel_rails:243 > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:488:in `load' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:488:in `load' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:342:in `new_constants_in' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:488:in `load' > /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/servers/ > mongrel.rb:60 > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `gem_original_require' > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `require' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:495:in `require' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:342:in `new_constants_in' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:495:in `require' > /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/ > server.rb:39 > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `gem_original_require' > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `require' > script/server:3 > RubyamfController: missing default helper path rubyamf_helper > > > Processing RubyamfController#gateway (for 127.0.0.1 at 2007-08-24 > 20:53:39) [POST] > Session ID: f3cb7796bd4e6cffe6fdfcf34cc0bae7 > Parameters: {"action"=>"gateway", "controller"=>"rubyamf"} > > > ArgumentError (wrong number of arguments (0 for 1)): > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:1096:in `render' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:1096:in `perform_action_without_filters' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/filters.rb:632:in `call_filter' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/filters.rb:619:in `perform_action_without_benchmark' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/benchmarking.rb:66:in > `perform_action_without_rescue' > /opt/local/lib/ruby/1.8/benchmark.rb:293:in `measure' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/benchmarking.rb:66:in > `perform_action_without_rescue' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/rescue.rb:83:in `perform_action' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:430:in `send' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:430:in `process_without_filters' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/filters.rb:624:in > `process_without_session_management_support' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/session_management.rb:114:in `process' > /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/base.rb:330:in `process' > /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/dispatcher.rb: > 41:in `dispatch' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > rails.rb:78:in `process' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > rails.rb:76:in `synchronize' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > rails.rb:76:in `process' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 618:in `process_client' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 617:in `each' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 617:in `process_client' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `initialize' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `new' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 736:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 720:in `initialize' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 720:in `new' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb: > 720:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > configurator.rb:271:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > configurator.rb:270:in `each' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > configurator.rb:270:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/ > mongrel_rails:127:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > command.rb:211:in `run' > /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/ > mongrel_rails:243 > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:488:in `load' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:488:in `load' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:342:in `new_constants_in' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:488:in `load' > /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/ > servers/mongrel.rb:60 > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `gem_original_require' > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `require' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:495:in `require' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:342:in `new_constants_in' > /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/ > active_support/dependencies.rb:495:in `require' > /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/ > server.rb:39 > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `gem_original_require' > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb: > 27:in `require' > script/server:3 > > > Rendering /opt/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/ > action_controller/templates/rescues/layout.rhtml (500 Internal Error) From grimm at grimmwerks.com Sat Aug 25 19:19:53 2007 From: grimm at grimmwerks.com (grimmwerks) Date: Sat, 25 Aug 2007 19:19:53 -0400 Subject: [Rubyamf-discussion] using scaffolding? Message-ID: Hey - is there a way I can just piggy back on the normal scaffold methods from Flex? From chuck at chuckfletcher.com Mon Aug 27 17:07:12 2007 From: chuck at chuckfletcher.com (Chuck Fletcher) Date: Mon, 27 Aug 2007 17:07:12 -0400 Subject: [Rubyamf-discussion] hi all Message-ID: <46D33D00.3040109@chuckfletcher.com> any pointers on how to call the new restful rubyamf functionality from actionscript 3? Any benefit to using SSR, or does that specifically need a gateway style call. Thanks, Chuck -- *Chuck Fletcher* Email: chuck at chuckfletcher.com Mobile: 646.369.9389 AIM: chuckfletc Linked In: chuckfletcher From beingthexemplary at gmail.com Mon Aug 27 17:50:16 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Mon, 27 Aug 2007 17:50:16 -0400 Subject: [Rubyamf-discussion] hi all In-Reply-To: <46D33D00.3040109@chuckfletcher.com> References: <46D33D00.3040109@chuckfletcher.com> Message-ID: RubyAMF isn't really "restful", so you're not able to call ( http://localhost:3000/controller/method.amf), Remoting must be used through NetConnection. using respond_to format for AMF and RubyAMF is actually returing your result to RubyAMF and being serialized then back throught the response. HTTPService class doesn't accept AMF is a response type, so it won't be deserialized. The benefit of SSR is just ease of use, using remote object you have to write an average of 10 lines, SSR is at the very least 2. max is usually about 4. And the interface is pretty simple, supplying callbacks VS listeners everywhere. -Aaron On 8/27/07, Chuck Fletcher wrote: > > any pointers on how to call the new restful rubyamf functionality from > actionscript 3? > > Any benefit to using SSR, or does that specifically need a gateway style > call. > > Thanks, > > Chuck > > > -- > *Chuck Fletcher* > Email: chuck at chuckfletcher.com > Mobile: 646.369.9389 > AIM: chuckfletc > Linked In: chuckfletcher > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070827/adad397e/attachment.html From beingthexemplary at gmail.com Mon Aug 27 23:28:17 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Mon, 27 Aug 2007 23:28:17 -0400 Subject: [Rubyamf-discussion] [Fwd: Re: hi all] In-Reply-To: References: <46D3497F.6000503@chuckfletcher.com> Message-ID: Hi Mark, If you wanted to use REST calls in Flex, you'd have to use HTTPService class. What you're doing with REST is a basic GET call over HTTP. SSR, is specifically for flash remoting, which is over HTTP but uses the binary AMF format. Where as REST uses xml, or rss, or whichever markup language you see fit. SSR wouldn't work with a true rails REST call like http://localhost:3000/user/show/1.xml Does that make sense / help? -Aaron On 8/27/07, aaron smith wrote: > > Hi Mark, > > If you wanted to use REST calls in Flex, you'd have to use HTTPService > class. What you're doing with REST is a basic GET call over HTTP. SSR, is > specifically for flash remoting, which is over HTTP but uses the binary AMF > format. Where as REST uses xml, or rss, or whichever markup language you see > fit. > > SSR wouldn't work with a true rails REST call like > http://localhost:3000/user/show/1.xml > > Does that make sense / help? > > -Aaron > > > > > On 8/27/07, Mark Llobrera wrote: > > > > Aaron- > > I'm working with Chuck on this and I have a few questions on the AS3 > > end. I've done a quick test example against RubyAMF which uses SSR. The > > script is (as you said) 2 lines long: > > > > rs = new RemotingService("http://localhost:3000/rubyamf/gateway", > > "TestWorldController"); > > rs.hello_world([], onResult, onFault); > > > > My question is, how would the service calls change if attempting to call > > a REST app and using SSR? Would the call still have to be proxied through > > the gateway? And if so, what do I do about the fact that there's no method > > call to make for my REST app (since that is what triggers everything in the > > vanilla RubyAMF example above)? A quick syntax example would be very > > helpful. Thanks much. > > > > -Mark > > On Aug 27, 2007, at 6:00 PM, Chuck Fletcher wrote: > > > > > > -- > > *Chuck Fletcher* > > Email: chuck at chuckfletcher.com > > > > > Mobile: 646.369.9389 > > AIM: chuckfletc > > Linked In: chuckfletcher < http://www.linkedin.com/in/chuckfletcher> > > ** > > *From: * "aaron smith" > > *Date: * August 27, 2007 5:50:16 PM EDT > > *To: * rubyamf-discussion at rubyforge.org > > *Subject: * *Re: [Rubyamf-discussion] hi all* > > > > > > RubyAMF isn't really "restful", so you're not able to call ( > > http://localhost:3000/controller/method.amf), Remoting must be used > > through NetConnection. using respond_to format for AMF and RubyAMF is > > actually returing your result to RubyAMF and being serialized then back > > throught the response. HTTPService class doesn't accept AMF is a response > > type, so it won't be deserialized. > > > > The benefit of SSR is just ease of use, using remote object you have to > > write an average of 10 lines, SSR is at the very least 2. max is usually > > about 4. And the interface is pretty simple, supplying callbacks VS > > listeners everywhere. > > > > -Aaron > > > > On 8/27/07, Chuck Fletcher < chuck at chuckfletcher.com> wrote: > > > > > > any pointers on how to call the new restful rubyamf functionality from > > > > > > actionscript 3? > > > > > > Any benefit to using SSR, or does that specifically need a gateway > > > style > > > call. > > > > > > Thanks, > > > > > > Chuck > > > > > > > > > -- > > > *Chuck Fletcher* > > > Email: chuck at chuckfletcher.com > > > Mobile: 646.369.9389 > > > AIM: chuckfletc < aim:goim?screenname=chuckfletc> > > > Linked In: chuckfletcher > > > _______________________________________________ > > > Rubyamf-discussion mailing list > > > Rubyamf-discussion at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > > > _______________________________________________ > > Rubyamf-discussion mailing list > > Rubyamf-discussion at rubyforge.org > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070827/c5700920/attachment.html From beingthexemplary at gmail.com Tue Aug 28 02:01:58 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Tue, 28 Aug 2007 02:01:58 -0400 Subject: [Rubyamf-discussion] RubyAMF 1.3 Release Candidate 1 Message-ID: Hello All, Please check out the latest info about RubyAMF 1.3RC1. http://blog.rubyamf.org/ -Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070828/6643bc86/attachment.html From chuck at chuckfletcher.com Tue Aug 28 07:56:00 2007 From: chuck at chuckfletcher.com (Chuck Fletcher) Date: Tue, 28 Aug 2007 07:56:00 -0400 Subject: [Rubyamf-discussion] [Fwd: Re: hi all] In-Reply-To: References: <46D3497F.6000503@chuckfletcher.com> Message-ID: <180FB0BA-4DE1-4165-9E84-9CF0E3CD90B2@chuckfletcher.com> Thanks Aaron, We are just using flash, no flex. We'd like to use SSR and respond_to style controllers. For example we have a model called events and setup a respond to :amf line on our index method. What would the SSR connection string be? Thanks, Chuck Sent from my iPhone On Aug 27, 2007, at 11:28 PM, "aaron smith" wrote: > Hi Mark, > > If you wanted to use REST calls in Flex, you'd have to use > HTTPService class. What you're doing with REST is a basic GET call > over HTTP. SSR, is specifically for flash remoting, which is over > HTTP but uses the binary AMF format. Where as REST uses xml, or rss, > or whichever markup language you see fit. > > SSR wouldn't work with a true rails REST call like http://localhost:3000/user/show/1.xml > > Does that make sense / help? > > -Aaron > > > > > > On 8/27/07, aaron smith < beingthexemplary at gmail.com> wrote: > Hi Mark, > > If you wanted to use REST calls in Flex, you'd have to use > HTTPService class. What you're doing with REST is a basic GET call > over HTTP. SSR, is specifically for flash remoting, which is over > HTTP but uses the binary AMF format. Where as REST uses xml, or rss, > or whichever markup language you see fit. > > SSR wouldn't work with a true rails REST call like http://localhost:3000/user/show/1.xml > > Does that make sense / help? > > -Aaron > > > > > > On 8/27/07, Mark Llobrera wrote: > Aaron- > > I'm working with Chuck on this and I have a few questions on the AS3 > end. I've done a quick test example against RubyAMF which uses SSR. > The script is (as you said) 2 lines long: > > rs = new RemotingService("http://localhost:3000/rubyamf/gateway", > "TestWorldController"); > rs.hello_world([], onResult, onFault); > > My question is, how would the service calls change if attempting to > call a REST app and using SSR? Would the call still have to be > proxied through the gateway? And if so, what do I do about the fact > that there's no method call to make for my REST app (since that is > what triggers everything in the vanilla RubyAMF example above)? A > quick syntax example would be very helpful. Thanks much. > > -Mark > On Aug 27, 2007, at 6:00 PM, Chuck Fletcher wrote: > >> >> -- >> *Chuck Fletcher* >> Email: chuck at chuckfletcher.com >> Mobile: 646.369.9389 >> AIM: chuckfletc >> Linked In: chuckfletcher < http://www.linkedin.com/in/chuckfletcher> >> >> From: "aaron smith" >> Date: August 27, 2007 5:50:16 PM EDT >> To: rubyamf-discussion at rubyforge.org >> Subject: Re: [Rubyamf-discussion] hi all >> >> >> RubyAMF isn't really "restful", so you're not able to call ( http://localhost:3000/controller/method.amf >> ), Remoting must be used through NetConnection. using respond_to >> format for AMF and RubyAMF is actually returing your result to >> RubyAMF and being serialized then back throught the response. >> HTTPService class doesn't accept AMF is a response type, so it >> won't be deserialized. >> >> The benefit of SSR is just ease of use, using remote object you >> have to write an average of 10 lines, SSR is at the very least 2. >> max is usually about 4. And the interface is pretty simple, >> supplying callbacks VS listeners everywhere. >> >> -Aaron >> >> On 8/27/07, Chuck Fletcher < chuck at chuckfletcher.com> wrote: >> any pointers on how to call the new restful rubyamf functionality >> from >> actionscript 3? >> >> Any benefit to using SSR, or does that specifically need a gateway >> style >> call. >> >> Thanks, >> >> Chuck >> >> >> -- >> *Chuck Fletcher* >> Email: chuck at chuckfletcher.com >> Mobile: 646.369.9389 >> AIM: chuckfletc < aim:goim?screenname=chuckfletc> >> Linked In: chuckfletcher >> _______________________________________________ >> Rubyamf-discussion mailing list >> Rubyamf-discussion at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rubyamf-discussion >> >> _______________________________________________ >> Rubyamf-discussion mailing list >> Rubyamf-discussion at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rubyamf-discussion >> >> > > > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070828/3ef09e87/attachment-0001.html From beingthexemplary at gmail.com Tue Aug 28 11:15:06 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Tue, 28 Aug 2007 11:15:06 -0400 Subject: [Rubyamf-discussion] [Fwd: Re: hi all] In-Reply-To: <180FB0BA-4DE1-4165-9E84-9CF0E3CD90B2@chuckfletcher.com> References: <46D3497F.6000503@chuckfletcher.com> <180FB0BA-4DE1-4165-9E84-9CF0E3CD90B2@chuckfletcher.com> Message-ID: Oh, sorry I didn't understand the question completely. The connection string doesn't change. Here is a simple example. FLASH: import org.rubyamf.remoting.ssr.* var service:RemotingService = new RemotingService(' http://localhost:3000/rubyamf/gateway','MyController'); service.addEventListener(FaultEvent.CONNECTION_ERROR, onConnectFault); service.addHeader('recordset_format',false,'fl9'); //call service service.index([], onresult, onfault); private function onConnectFault(fe:FaultEvent):void{} private function onresult(re:ResultEvent):void { trace(re.result): } private function onfault(fe:FaultEvent):void { trace(fe.fault.faultString); } RAILS::: class MyController [var] } end end end Check out these examples, this should be enough to get you started. Also check out these links: http://wiki.rubyamf.org/wiki/show/RecordSetFormat http://wiki.rubyamf.org/wiki/show/AmfRest regards, -Aaron On 8/28/07, Chuck Fletcher wrote: > > Thanks Aaron, > > We are just using flash, no flex. > > We'd like to use SSR and respond_to style controllers. > > For example we have a model called events and setup a respond to :amf line > on our index method. > > What would the SSR connection string be? > > Thanks, > > Chuck > > Sent from my iPhone > > On Aug 27, 2007, at 11:28 PM, "aaron smith" > wrote: > > Hi Mark, > > If you wanted to use REST calls in Flex, you'd have to use HTTPService > class. What you're doing with REST is a basic GET call over HTTP. SSR, is > specifically for flash remoting, which is over HTTP but uses the binary AMF > format. Where as REST uses xml, or rss, or whichever markup language you see > fit. > > SSR wouldn't work with a true rails REST call like > > http://localhost:3000/user/show/1.xml > > Does that make sense / help? > > -Aaron > > > > > > On 8/27/07, aaron smith < > beingthexemplary at gmail.com> wrote: > > > > Hi Mark, > > > > If you wanted to use REST calls in Flex, you'd have to use HTTPService > > class. What you're doing with REST is a basic GET call over HTTP. SSR, is > > specifically for flash remoting, which is over HTTP but uses the binary AMF > > format. Where as REST uses xml, or rss, or whichever markup language you see > > fit. > > > > SSR wouldn't work with a true rails REST call like > > > > http://localhost:3000/user/show/1.xml > > > > Does that make sense / help? > > > > -Aaron > > > > > > > > > > On 8/27/07, Mark Llobrera < > > mllobrera at domanistudios.com > wrote: > > > > > > Aaron- > > > I'm working with Chuck on this and I have a few questions on the AS3 > > > end. I've done a quick test example against RubyAMF which uses SSR. The > > > script is (as you said) 2 lines long: > > > > > > rs = new RemotingService(" > > > http://localhost:3000/rubyamf/gateway", "TestWorldController"); > > > rs.hello_world([], onResult, onFault); > > > > > > My question is, how would the service calls change if attempting to > > > call a REST app and using SSR? Would the call still have to be proxied > > > through the gateway? And if so, what do I do about the fact that there's no > > > method call to make for my REST app (since that is what triggers everything > > > in the vanilla RubyAMF example above)? A quick syntax example would be very > > > helpful. Thanks much. > > > > > > -Mark > > > On Aug 27, 2007, at 6:00 PM, Chuck Fletcher wrote: > > > > > > > > > -- > > > *Chuck Fletcher* > > > Email: chuck at chuckfletcher.com > > > chuck at chuckfletcher.com> > > > Mobile: 646.369.9389 > > > AIM: chuckfletc > > > Linked In: chuckfletcher < > > > http://www.linkedin.com/in/chuckfletcher> > > > ** > > > *From: * "aaron smith" < > > > beingthexemplary at gmail.com> > > > *Date: * August 27, 2007 5:50:16 PM EDT > > > *To: * > > > rubyamf-discussion at rubyforge.org > > > *Subject: * *Re: [Rubyamf-discussion] hi all* > > > > > > > > > RubyAMF isn't really "restful", so you're not able to call ( > > > > > > http://localhost:3000/controller/method.amf), Remoting must be used > > > through NetConnection. using respond_to format for AMF and RubyAMF is > > > actually returing your result to RubyAMF and being serialized then back > > > throught the response. HTTPService class doesn't accept AMF is a response > > > type, so it won't be deserialized. > > > > > > The benefit of SSR is just ease of use, using remote object you have > > > to write an average of 10 lines, SSR is at the very least 2. max is usually > > > about 4. And the interface is pretty simple, supplying callbacks VS > > > listeners everywhere. > > > > > > -Aaron > > > > > > On 8/27/07, Chuck Fletcher < > > > chuck at chuckfletcher.com> wrote: > > > > > > > > any pointers on how to call the new restful rubyamf functionality > > > > from > > > > actionscript 3? > > > > > > > > Any benefit to using SSR, or does that specifically need a gateway > > > > style > > > > call. > > > > > > > > Thanks, > > > > > > > > Chuck > > > > > > > > > > > > -- > > > > *Chuck Fletcher* > > > > Email: chuck at chuckfletcher.com > > > > chuck at chuckfletcher.com> > > > > Mobile: 646.369.9389 > > > > AIM: chuckfletc < aim:goim?screenname=chuckfletc> > > > > Linked In: chuckfletcher < > > > > http://www.linkedin.com/in/chuckfletcher > > > > > _______________________________________________ > > > > Rubyamf-discussion mailing list > > > > Rubyamf-discussion at rubyforge.org > > > > > > > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > > > > > > _______________________________________________ > > > Rubyamf-discussion mailing list > > > Rubyamf-discussion at rubyforge.org > > > > > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > > > > > > > > > > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070828/a87660f4/attachment.html From beingthexemplary at gmail.com Tue Aug 28 11:17:04 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Tue, 28 Aug 2007 11:17:04 -0400 Subject: [Rubyamf-discussion] [flexiblerails] RubyAMF 1.3 Release Candidate 1 In-Reply-To: <119169.27116.qm@web57609.mail.re1.yahoo.com> References: <119169.27116.qm@web57609.mail.re1.yahoo.com> Message-ID: Yep - I will be putting up some screencast in a couple days. -Aaron On 8/28/07, Brent Schooley wrote: > > Is there any chance you will have tutorials up soon for 1.3? This is my > first version trying RubyAMF so even a Hello World would be great. I want to > make sure I learn RubyAMF the way you intend for it to be used. > > Thanks, > Brent > > Sent from my iPhone > > On Aug 28, 2007, at 2:01 AM, "aaron smith" > wrote: > > Hello All, > > Please check out the latest info about RubyAMF 1.3RC1. > > http://blog.rubyamf.org/ > -Aaron > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "flexiblerails" group. > To post to this group, send email to flexiblerails at googlegroups.com > To unsubscribe from this group, send email to > flexiblerails-unsubscribe at googlegroups.com > For more options, visit this group at > http://groups.google.com/group/flexiblerails?hl=en > -~----------~----~----~----~------~----~------~--~--- > > > > > > > ____________________________________________________________________________________ > Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, > news, photos & more. > http://mobile.yahoo.com/go?refer=1GNXIC -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070828/ce10fa7c/attachment-0001.html From beingthexemplary at gmail.com Tue Aug 28 12:19:25 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Tue, 28 Aug 2007 12:19:25 -0400 Subject: [Rubyamf-discussion] [Fwd: Re: hi all] In-Reply-To: References: <46D3497F.6000503@chuckfletcher.com> <180FB0BA-4DE1-4165-9E84-9CF0E3CD90B2@chuckfletcher.com> Message-ID: I just put up a new version of SSR, couple fixes. Most notably, the Connection Error event wasn't being dispatched correctly.. ssr.riaforge.org -A On 8/28/07, aaron smith wrote: > > Oh, sorry I didn't understand the question completely. The connection > string doesn't change. Here is a simple example. > > FLASH: > import org.rubyamf.remoting.ssr.* > var service:RemotingService = new RemotingService(' > http://localhost:3000/rubyamf/gateway','MyController' > ); > service.addEventListener(FaultEvent.CONNECTION_ERROR, onConnectFault); > service.addHeader('recordset_format',false,'fl9'); > > //call service > service.index([], onresult, onfault); > > private function onConnectFault(fe:FaultEvent):void{} > > private function onresult(re:ResultEvent):void > { > trace(re.result): > } > > private function onfault(fe:FaultEvent):void > { > trace(fe.fault.faultString); > } > > > RAILS::: > class MyController def index > if @is_amf > ##MY RubyAMF Specific LOGIC > else > #MY xml/html/whatever LOGIC > end > respond_to do |format| > format.amf { render :amf => [var] } > end > end > end > > > Check out these examples, this should be enough to get you started. Also > check out these links: > > http://wiki.rubyamf.org/wiki/show/RecordSetFormat > http://wiki.rubyamf.org/wiki/show/AmfRest > > regards, > -Aaron > > > > > On 8/28/07, Chuck Fletcher wrote: > > > > Thanks Aaron, > > > > We are just using flash, no flex. > > > > We'd like to use SSR and respond_to style controllers. > > > > For example we have a model called events and setup a respond to :amf > > line on our index method. > > > > What would the SSR connection string be? > > > > Thanks, > > > > Chuck > > > > Sent from my iPhone > > > > On Aug 27, 2007, at 11:28 PM, "aaron smith" < beingthexemplary at gmail.com> > > wrote: > > > > Hi Mark, > > > > If you wanted to use REST calls in Flex, you'd have to use HTTPService > > class. What you're doing with REST is a basic GET call over HTTP. SSR, is > > specifically for flash remoting, which is over HTTP but uses the binary AMF > > format. Where as REST uses xml, or rss, or whichever markup language you see > > fit. > > > > SSR wouldn't work with a true rails REST call like > > http://localhost:3000/user/show/1.xml > > > > Does that make sense / help? > > > > -Aaron > > > > > > > > > > > > On 8/27/07, aaron smith < > > beingthexemplary at gmail.com> wrote: > > > > > > Hi Mark, > > > > > > If you wanted to use REST calls in Flex, you'd have to use HTTPService > > > class. What you're doing with REST is a basic GET call over HTTP. SSR, is > > > specifically for flash remoting, which is over HTTP but uses the binary AMF > > > format. Where as REST uses xml, or rss, or whichever markup language you see > > > fit. > > > > > > SSR wouldn't work with a true rails REST call like > > > http://localhost:3000/user/show/1.xml > > > > > > Does that make sense / help? > > > > > > -Aaron > > > > > > > > > > > > > > > On 8/27/07, Mark Llobrera < mllobrera at domanistudios.com> wrote: > > > > > > > > Aaron- > > > > I'm working with Chuck on this and I have a few questions on the AS3 > > > > end. I've done a quick test example against RubyAMF which uses SSR. The > > > > script is (as you said) 2 lines long: > > > > > > > > rs = new RemotingService(" http://localhost:3000/rubyamf/gateway", > > > > "TestWorldController"); > > > > rs.hello_world([], onResult, onFault); > > > > > > > > My question is, how would the service calls change if attempting to > > > > call a REST app and using SSR? Would the call still have to be proxied > > > > through the gateway? And if so, what do I do about the fact that there's no > > > > method call to make for my REST app (since that is what triggers everything > > > > in the vanilla RubyAMF example above)? A quick syntax example would be very > > > > helpful. Thanks much. > > > > > > > > -Mark > > > > On Aug 27, 2007, at 6:00 PM, Chuck Fletcher wrote: > > > > > > > > > > > > -- > > > > *Chuck Fletcher* > > > > Email: chuck at chuckfletcher.com chuck at chuckfletcher.com > > > > > > > > > Mobile: 646.369.9389 > > > > AIM: chuckfletc > > > > Linked In: chuckfletcher < > > > > > > > > http://www.linkedin.com/in/chuckfletcher> > > > > ** > > > > *From: * "aaron smith" < beingthexemplary at gmail.com > > > > > > > > > *Date: * August 27, 2007 5:50:16 PM EDT > > > > *To: * rubyamf-discussion at rubyforge.org > > > > *Subject: * *Re: [Rubyamf-discussion] hi all* > > > > > > > > > > > > RubyAMF isn't really "restful", so you're not able to call ( > > > > http://localhost:3000/controller/method.amf), > > > > Remoting must be used through NetConnection. using respond_to format for AMF > > > > and RubyAMF is actually returing your result to RubyAMF and being serialized > > > > then back throught the response. HTTPService class doesn't accept AMF is a > > > > response type, so it won't be deserialized. > > > > > > > > The benefit of SSR is just ease of use, using remote object you have > > > > to write an average of 10 lines, SSR is at the very least 2. max is usually > > > > about 4. And the interface is pretty simple, supplying callbacks VS > > > > listeners everywhere. > > > > > > > > -Aaron > > > > > > > > On 8/27/07, Chuck Fletcher < > > > > chuck at chuckfletcher.com> wrote: > > > > > > > > > > any pointers on how to call the new restful rubyamf functionality > > > > > from > > > > > actionscript 3? > > > > > > > > > > Any benefit to using SSR, or does that specifically need a gateway > > > > > style > > > > > call. > > > > > > > > > > Thanks, > > > > > > > > > > Chuck > > > > > > > > > > > > > > > -- > > > > > *Chuck Fletcher* > > > > > Email: chuck at chuckfletcher.com > > > > chuck at chuckfletcher.com> > > > > > Mobile: 646.369.9389 > > > > > AIM: chuckfletc < aim:goim?screenname=chuckfletc> > > > > > Linked In: chuckfletcher <http://www.linkedin.com/in/chuckfletcher> > > > > > _______________________________________________ > > > > > Rubyamf-discussion mailing list > > > > > > > > > > Rubyamf-discussion at rubyforge.org > > > > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > > > > > > > > > _______________________________________________ > > > > Rubyamf-discussion mailing list > > > > Rubyamf-discussion at rubyforge.org > > > > > > > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Rubyamf-discussion mailing list > > Rubyamf-discussion at rubyforge.org > > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070828/9ebc07e9/attachment.html From mllobrera at domanistudios.com Tue Aug 28 12:48:10 2007 From: mllobrera at domanistudios.com (Mark Llobrera) Date: Tue, 28 Aug 2007 12:48:10 -0400 Subject: [Rubyamf-discussion] [Fwd: Re: hi all] In-Reply-To: References: <46D3497F.6000503@chuckfletcher.com> <180FB0BA-4DE1-4165-9E84-9CF0E3CD90B2@chuckfletcher.com> Message-ID: <7918C666-2133-4F56-A756-4FF14B170347@domanistudios.com> Thanks for the AS3 example - that worked great. -Mark On Aug 28, 2007, at 12:19 PM, aaron smith wrote: > I just put up a new version of SSR, couple fixes. Most notably, the > Connection Error event wasn't being dispatched correctly.. > > ssr.riaforge.org > -A > > On 8/28/07, aaron smith wrote: > Oh, sorry I didn't understand the question completely. The > connection string doesn't change. Here is a simple example. > > FLASH: > import org.rubyamf.remoting.ssr.* > var service:RemotingService = new RemotingService(' http:// > localhost:3000/rubyamf/gateway','MyController'); > service.addEventListener (FaultEvent.CONNECTION_ERROR, > onConnectFault); > service.addHeader('recordset_format',false,'fl9'); > > //call service > service.index([], onresult, onfault); > > private function onConnectFault(fe:FaultEvent):void{} > > private function onresult(re:ResultEvent):void > { > trace(re.result): > } > > private function onfault(fe:FaultEvent):void > { > trace(fe.fault.faultString); > } > > > RAILS::: > class MyController def index > if @is_amf > ##MY RubyAMF Specific LOGIC > else > #MY xml/html/whatever LOGIC > end > respond_to do |format| > format.amf { render :amf => [var] } > end > end > end > > > Check out these examples, this should be enough to get you started. > Also check out these links: > > http://wiki.rubyamf.org/wiki/show/RecordSetFormat > http://wiki.rubyamf.org/wiki/show/AmfRest > > regards, > -Aaron > > > > > > On 8/28/07, Chuck Fletcher < chuck at chuckfletcher.com> wrote: > Thanks Aaron, > > We are just using flash, no flex. > > We'd like to use SSR and respond_to style controllers. > > For example we have a model called events and setup a respond > to :amf line on our index method. > > What would the SSR connection string be? > > Thanks, > > Chuck > > Sent from my iPhone > > On Aug 27, 2007, at 11:28 PM, "aaron smith" < > beingthexemplary at gmail.com> wrote: > >> Hi Mark, >> >> If you wanted to use REST calls in Flex, you'd have to use >> HTTPService class. What you're doing with REST is a basic GET call >> over HTTP. SSR, is specifically for flash remoting, which is over >> HTTP but uses the binary AMF format. Where as REST uses xml, or >> rss, or whichever markup language you see fit. >> >> SSR wouldn't work with a true rails REST call like http:// >> localhost:3000/user/show/1.xml >> >> Does that make sense / help? >> >> -Aaron >> >> >> >> >> >> On 8/27/07, aaron smith < beingthexemplary at gmail.com> wrote: >> Hi Mark, >> >> If you wanted to use REST calls in Flex, you'd have to use >> HTTPService class. What you're doing with REST is a basic GET call >> over HTTP. SSR, is specifically for flash remoting, which is over >> HTTP but uses the binary AMF format. Where as REST uses xml, or >> rss, or whichever markup language you see fit. >> >> SSR wouldn't work with a true rails REST call like http:// >> localhost:3000/user/show/1.xml >> >> Does that make sense / help? >> >> -Aaron >> >> >> >> >> >> On 8/27/07, Mark Llobrera < mllobrera at domanistudios.com > wrote: >> Aaron- >> >> I'm working with Chuck on this and I have a few questions on the >> AS3 end. I've done a quick test example against RubyAMF which uses >> SSR. The script is (as you said) 2 lines long: >> >> rs = new RemotingService(" http://localhost:3000/rubyamf/gateway", >> "TestWorldController"); >> rs.hello_world([], onResult, onFault); >> >> My question is, how would the service calls change if attempting >> to call a REST app and using SSR? Would the call still have to be >> proxied through the gateway? And if so, what do I do about the >> fact that there's no method call to make for my REST app (since >> that is what triggers everything in the vanilla RubyAMF example >> above)? A quick syntax example would be very helpful. Thanks much. >> >> -Mark >> On Aug 27, 2007, at 6:00 PM, Chuck Fletcher wrote: >> >>> >>> -- >>> *Chuck Fletcher* >>> Email: chuck at chuckfletcher.com >>> Mobile: 646.369.9389 >>> AIM: chuckfletc >>> Linked In: chuckfletcher < http://www.linkedin.com/in/chuckfletcher> >>> >>> From: "aaron smith" < beingthexemplary at gmail.com> >>> Date: August 27, 2007 5:50:16 PM EDT >>> To: rubyamf-discussion at rubyforge.org >>> Subject: Re: [Rubyamf-discussion] hi all >>> >>> >>> RubyAMF isn't really "restful", so you're not able to call >>> ( http://localhost:3000/controller/method.amf), Remoting must be >>> used through NetConnection. using respond_to format for AMF and >>> RubyAMF is actually returing your result to RubyAMF and being >>> serialized then back throught the response. HTTPService class >>> doesn't accept AMF is a response type, so it won't be deserialized. >>> >>> The benefit of SSR is just ease of use, using remote object you >>> have to write an average of 10 lines, SSR is at the very least 2. >>> max is usually about 4. And the interface is pretty simple, >>> supplying callbacks VS listeners everywhere. >>> >>> -Aaron >>> >>> On 8/27/07, Chuck Fletcher < chuck at chuckfletcher.com> wrote: >>> any pointers on how to call the new restful rubyamf functionality >>> from >>> actionscript 3? >>> >>> Any benefit to using SSR, or does that specifically need a >>> gateway style >>> call. >>> >>> Thanks, >>> >>> Chuck >>> >>> >>> -- >>> *Chuck Fletcher* >>> Email: chuck at chuckfletcher.com >>> Mobile: 646.369.9389 >>> AIM: chuckfletc < aim:goim?screenname=chuckfletc> >>> Linked In: chuckfletcher < http://www.linkedin.com/in/ >>> chuckfletcher > >>> _______________________________________________ >>> Rubyamf-discussion mailing list >>> Rubyamf-discussion at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/rubyamf-discussion >>> >>> _______________________________________________ >>> Rubyamf-discussion mailing list >>> Rubyamf-discussion at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/rubyamf-discussion >>> >>> >> >> >> >> _______________________________________________ >> Rubyamf-discussion mailing list >> Rubyamf-discussion at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rubyamf-discussion > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070828/165f8ffb/attachment-0001.html From seth at 4thtemple.com Thu Aug 30 01:55:24 2007 From: seth at 4thtemple.com (seth) Date: Thu, 30 Aug 2007 01:55:24 -0400 Subject: [Rubyamf-discussion] rubyamf + ssr Message-ID: <20070830015524.5c3ae1da.seth@4thtemple.com> I'm following the example from Http://www.dirtystylus.com/blogs, but the app stalls and says "waiting for localhost" the test rubyamf/gateway works fine. is there any special compiler options i need to pass to mxmlc? From mllobrera at domanistudios.com Thu Aug 30 09:48:19 2007 From: mllobrera at domanistudios.com (Mark Llobrera) Date: Thu, 30 Aug 2007 09:48:19 -0400 Subject: [Rubyamf-discussion] rubyamf + ssr In-Reply-To: <20070830015524.5c3ae1da.seth@4thtemple.com> References: <20070830015524.5c3ae1da.seth@4thtemple.com> Message-ID: Forgot to cc the list on my reply to Seth, just in case someone has another idea he might try. On Aug 30, 2007, at 1:55 AM, seth wrote: > I'm following the example from Http://www.dirtystylus.com/blogs, > but the app stalls and says "waiting for localhost" the test > rubyamf/gateway works fine. is there any special compiler options > i need to pass to mxmlc? I'm not passing any extra params to mxmlc. As a sanity check on the compiler end I tried this from the Flash IDE as well, by setting RemotingTest as the document class, and it succeeded. The first thing I would check is to make sure that you can make calls out to localhost from Flash. Perhaps you can try loading a text/xml file from localhost. At first I thought it might be something silly like a port number mismatch (Locomotive defaults to 3001, not 3000) but on testing that hypothesis I saw that you get a proper "onConnectionStatus: NetConnection.Call.Failed" message, so that's most likely not what you're facing. Let me know how that shakes out for you. -Mark From seth at 4thtemple.com Thu Aug 30 10:17:44 2007 From: seth at 4thtemple.com (seth) Date: Thu, 30 Aug 2007 10:17:44 -0400 Subject: [Rubyamf-discussion] rubyamf + ssr In-Reply-To: References: <20070830015524.5c3ae1da.seth@4thtemple.com> Message-ID: <20070830101744.d638a7a4.seth@4thtemple.com> Ok, maybe it was late last night and I didnt see the error thrown: ActionController::RoutingError (no route found to match "/crossdomain.xml" with {:method=>:get}): All i had to do was copy the crossdomain.xml into /public and it was good to go. Thanks alot for this great plugin and tutorials to use it! On Thu, 30 Aug 2007 09:48:19 -0400 Mark Llobrera wrote: > Forgot to cc the list on my reply to Seth, just in case someone has > another idea he might try. > > On Aug 30, 2007, at 1:55 AM, seth wrote: > > > I'm following the example from Http://www.dirtystylus.com/blogs, > > but the app stalls and says "waiting for localhost" the test > > rubyamf/gateway works fine. is there any special compiler options > > i need to pass to mxmlc? > > I'm not passing any extra params to mxmlc. As a sanity check on the > compiler end I tried this from the Flash IDE as well, by setting > RemotingTest as the document class, and it succeeded. The first thing > I would check is to make sure that you can make calls out to > localhost from Flash. Perhaps you can try loading a text/xml file > from localhost. > > At first I thought it might be something silly like a port number > mismatch (Locomotive defaults to 3001, not 3000) but on testing that > hypothesis I saw that you get a proper "onConnectionStatus: > NetConnection.Call.Failed" message, so that's most likely not what > you're facing. > > Let me know how that shakes out for you. > > -Mark > > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion From mllobrera at domanistudios.com Thu Aug 30 10:25:20 2007 From: mllobrera at domanistudios.com (Mark Llobrera) Date: Thu, 30 Aug 2007 10:25:20 -0400 Subject: [Rubyamf-discussion] rubyamf + ssr In-Reply-To: <20070830101744.d638a7a4.seth@4thtemple.com> References: <20070830015524.5c3ae1da.seth@4thtemple.com> <20070830101744.d638a7a4.seth@4thtemple.com> Message-ID: <8857DEF0-1418-4779-80AD-984491C11AF5@domanistudios.com> On Aug 30, 2007, at 10:17 AM, seth wrote: > Ok, maybe it was late last night and I didnt see the error thrown: > ActionController::RoutingError (no route found to match "/ > crossdomain.xml" with {:method=>:get}): > All i had to do was copy the crossdomain.xml into /public and it > was good to go. Thanks alot for this great plugin and tutorials to > use it! Ah, that explains it - I'll put a quick note on my post reminding people to do this. Curiously on my install it didn't balk without the crossdomain policy file. And I definitely echo the thanks to Aaron for the screencasts and tutorials. -Mark From beingthexemplary at gmail.com Thu Aug 30 11:26:35 2007 From: beingthexemplary at gmail.com (aaron smith) Date: Thu, 30 Aug 2007 11:26:35 -0400 Subject: [Rubyamf-discussion] rubyamf + ssr In-Reply-To: <8857DEF0-1418-4779-80AD-984491C11AF5@domanistudios.com> References: <20070830015524.5c3ae1da.seth@4thtemple.com> <20070830101744.d638a7a4.seth@4thtemple.com> <8857DEF0-1418-4779-80AD-984491C11AF5@domanistudios.com> Message-ID: I'll put an update in the Rails installer to copy the crossdomain.xml to public. Thanks -Aaron On 8/30/07, Mark Llobrera wrote: > > On Aug 30, 2007, at 10:17 AM, seth wrote: > > > Ok, maybe it was late last night and I didnt see the error thrown: > > ActionController::RoutingError (no route found to match "/ > > crossdomain.xml" with {:method=>:get}): > > All i had to do was copy the crossdomain.xml into /public and it > > was good to go. Thanks alot for this great plugin and tutorials to > > use it! > > Ah, that explains it - I'll put a quick note on my post reminding > people to do this. Curiously on my install it didn't balk without the > crossdomain policy file. And I definitely echo the thanks to Aaron > for the screencasts and tutorials. > > -Mark > _______________________________________________ > Rubyamf-discussion mailing list > Rubyamf-discussion at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyamf-discussion > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyamf-discussion/attachments/20070830/1aa7884b/attachment.html