Hi David,

On Tue, 2009-08-04 at 10:58 -0700, InventoryTrackers wrote:
> Fred,
> Are you saying there's a way to call 'ruby script/server' with some
> extension to make this server apparent to other users on a Windows
> network?

You don't need an extension.

> I've never seen how one can call someone elses' 127.0.0.1 from another
> machine.

As long as they know your machine's IP address and you don't have your
ports blocked, they can access the app.  Assuming your IP is
XXX.XX.XXX.XX and you start mongrel on port 3000, anyone on your subnet
can access your app by typing http://XXX.XX.XXX.XX:3000 into their
browser address bar.

HTH,
Bill


> Are you aware of any articles or sources that might shed light on
> this?
> Thank you,
> David
> 
> On Aug 4, 7:57 am, Frederick Cheung <[email protected]>
> wrote:
> > On Aug 4, 2:18 pm, InventoryTrackers <[email protected]>
> > wrote:
> >
> > > I'm one of the unmentionable users that has been developing in Windows
> > > for the last 3 years. We all know that I can start a DOS script/server
> > > session on my machine and run the Rails application on my local
> > > browser.
> > > Is there a way that other Windows users could somehow 'pipe' onto this
> > > DOS session running and point THEIR browsers to it?
> > > Obviously, I'm exploring the 'holy grail' to see if we can run multi-
> > > user implementations in a Windows environment.
> >
> > Why would you need to do anything crazy at all - it's still running a
> > perfectly normal web server (it may be default bind to localhost but
> > that's just an option you pass to script/server)
> >
> > Fred
> >
> > > Many thanks,
> > > David
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to