On Aug 4, 6:58 pm, InventoryTrackers <[email protected]>
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?
> I've never seen how one can call someone elses' 127.0.0.1 from another
> machine.

Well it won't be magically visible. You just need to know their ip
address and stick http://something:3000 into a browser (like i said
you might need to make it bind to 0.0.0.0 first)

Fred
> 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