World: r3wp
[!Cheyenne] Discussions about the Cheyenne Web Server
older newer | first last |
Joe 29-May-2008 [2619x2] | doc, in erlang concurrency is supported in the programming language (i.e. does not use the os mechanisms). I am trying to track down a reference were it explained you could have 2 power 32 connections theoretically |
Maarten, yes you can set the secret cookie but if one system is compromised the whole distributed system is. how is that different in other architectures ? | |
Dockimbel 30-May-2008 [2621] | Unless Erlang implements its own TCP/IP stack, he will hit OS limitations, even if, internally, he's able to handle 2^32 connections. Anyway, I'm interested in reading such paper if you find it. |
Joe 30-May-2008 [2622x2] | not found the paper yet but here is an answer i found on the net |
Pat e wrote: > Can anyone tell me how can Yaws have almost 80,000 concurrent > connections, and some "home-made" erlang servers over 110K concurrent > connections if there are only 64,000 tcp/ip ports? A TCP/IP connection is identified on each host by a (local port, local IP, remote port, remote IP) tuple. Therefore, there can be more than 2^16 connections to a server (even if the server is listening on a fixed port) provided that they are from more than one client. In theory it's also possible to have more than 2^16 connections between a specific pair of hosts provided that they use all of the available port combinations. However, TCP/IP stacks generally do not support reusing local port numbers (when the port is not specified by the client software) by default, so the practical restriction in this case may still be 2^16. -- David Hopwood | |
Pekr 30-May-2008 [2624] | Sorry, but possible number of theoretical connection numbers is totally stupid reasoning for whatever kind of decision :-) |
Terry 30-May-2008 [2625] | Handling 64,000+ concurrent clients is a problem I wish I had. |
Dockimbel 30-May-2008 [2626x2] | Yep, in real world, there's no point accepting more than 10k connection on a single server. You usually hit memory and cpu limits far before reaching that limit. Spreading the load among multiple servers is the way to go. That's why the Yaws vs Apache benchmark sounds so theorical and irrelevant to me. |
theorical => theoretical | |
Gregg 30-May-2008 [2628] | I like "theorical", it sounds like "the oracle". :-) |
Joe 3-Jun-2008 [2629x2] | the yaws vs apache benchmark is more an example on how the erlang service can handle DoS |
hi doc, I have a c++ backg. and seen plenty fo 30k+ concurrent but yes for web sites its common to have a hw redirector and multiple servers | |
Chris 4-Jun-2008 [2631] | I'm back at asking this -- how do I obtain the original request string -- e.g. "/wiki/show/This_Page" within the CGI environment? 'path-info only gives me the translated filename (always '/qm.r' for my app) |
Dockimbel 5-Jun-2008 [2632] | Chris, you should test using http://localhost/show.cgiscript it will display all CGI data. 'script-name should give you what you need. |
Oldes 13-Jun-2008 [2633x3] | There must be: set 'NT-service? false in misc/os.r in the block where the 'library component is not found. (to be able boot with Rebol/Core) |
Let's say I need some functions available for all CGI scripts, where is the best place to init them? | |
(if I don't want to init them in all cgi scripts) | |
Dockimbel 14-Jun-2008 [2636x2] | CGI environment is not supposed to be persistent, so there's no other ways than to manually add libs loading code to %CGI.r script. If you're encapping Cheyenne, you can add your libs to %cheyenne.r (and don't forget to LOAD them too). If you need a persistent environment, use RSP instead. |
Thanks for the 'NT-Service? fix, it will be included in the next release. | |
Terry 16-Jun-2008 [2638x3] | Think we might try using Cheyenne as a personal web server, providing functionality similar to Adobe Air, Google Gears for our product. |
Here's a little video clip of a prototype in action.. http://kommonwealth.com/video/cheyennewidgetdemo.swf | |
That's all taking place in the browser, being served up from our server.. and accessing a copy of Cheyenne running locally. No cross-domain issues here :) | |
Pekr 16-Jun-2008 [2641] | Firewall problems? You have to allow listening port ... but - that should not be problem for 99% of users imo ... |
Oldes 16-Jun-2008 [2642x5] | Flash has very strict security. You have to setup it correctly to anable cross-domain functionality. It's not bad if you understand how it works. |
It has nothing to do with Firewalls. | |
http://www.adobe.com/devnet/flashplayer/articles/flash_player_9_security.pdf (but it's not related to Cheyenne) | |
Basically it's the part which was showstoper for Rebol plugin - shortly it works in a way, that if you want to connect to some site with Flash, Flash first loads crossdomain.xml file from the target server where must be your domain allowed to access the server domain. If it's not allowed, the Flash do not connects at all. It's a basic prevention of doing Dos attacks from Flash Player. | |
I'm not sure what is Terry doing, but of course you can use Rebol to connect from Flash to services on servers from not allowed domain as with Rebol you can change the request header easily. | |
Pekr 16-Jun-2008 [2647x2] | what are you talking about, Oldes? And yes, it has something to do with firewalls. The thing is - noone was talking flash here ;-) |
Terry imo wants to use Cheyenne as local web server, and to allow their kommonwealth to run locally cached, or something like that - but still - his technologies are html, css, js, ajax .... | |
Terry 16-Jun-2008 [2649] | yeah, Pekr's right. There's no flash there. I suppose the firewall would be an issue for some. |
Henrik 15-Jul-2008 [2650] | DocKimbel, small request: Would it be possible to post the rsp guide, cheatsheet and docs as separate pages directly on the site? It's unpractical to have to download Cheyenne every time I switch machine, just to read the docs. Thanks. |
Graham 15-Jul-2008 [2651] | stick them on google as a googledoc :) |
Dockimbel 15-Jul-2008 [2652x2] | Henrik: good suggestion |
RSP API document now online at : http://cheyenne-server.org/docs/rsp-api.html | |
Henrik 15-Jul-2008 [2654] | cool |
Dockimbel 4-Aug-2008 [2655x4] | Cheyenne Wiki is online : http://cheyenne-server.org/wiki.php |
It's running on the latest version 0.9.19 (not yet released) with php 5.2.6. | |
The wiki engine is PmWiki. | |
If you want to contribute by writing docs for Cheyenne, please ask me privately for an account. | |
Graham 4-Aug-2008 [2659] | Pretty neat demo of php in action with Cheyenne |
Dockimbel 4-Aug-2008 [2660] | Yep, it's quite fast, but will be faster when the FastCGI code will be optimized. |
Graham 4-Aug-2008 [2661] | can cheyenne be used to spawn a new task for a 3rd party application? |
Dockimbel 4-Aug-2008 [2662x3] | Yes, that's the purpose of mod-extapp. |
It has been improved in the upcoming Cheyenne release (0.9.19). | |
Mod-extapp can launch and kill 3rd party apps automatically. | |
Graham 4-Aug-2008 [2665x3] | My EMR has to do things like play back speech files etc, but I can't do it inside the app as it will kill the async. |
So, at present I'm using the mini webserver to play back sound and do voice recording. | |
Well, looking forward to new release then :) | |
Dockimbel 4-Aug-2008 [2668] | You could rely also on Uniserve's task-master to execute blocking tasks. |
older newer | first last |