Jump to content

AliceWonder32

New Members
  • Posts

    8
  • Joined

  • Last visited

AliceWonder32's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. Thanks. I wonder if a pecl wrapper could be written to solve this issue, e.g. the wrapper provides something that looks and behaves like a socket but proxies multiple sockets, so you create and bind multiple sockets, and then the wrapper socket listens on them much like binding to 0.0.0.0:port would do.
  2. Working on php socket server. New to sockets. Would love to support IPv6 in addition to IPv4. Sure, I could proxy IPv6 requests to IPv4 but I'd rather not. Can I bind the same socket to more than one IP:port ??
  3. I now have a CLI php based socket server doing much of what I want (rest is matter of finishing my code), thank you kicken for the suggestion.
  4. The point is that by using the same language for all things in the web app, code can be shared. For example, the class for session handling (I keep session info in a database), database connection, etc. so that future maintenance of the web application does not require changes to the php side of things and then the Javascript port of the php side of things. You can update a single class that both the main web app and the server side EventSource page. Of course the web developer needs to know Javascript for the client side programming, but the client side programming doesn't interface with server resources directly, it sends those as requests to the web application. If I have to do that part of the web app in node.js I'll do it in node.js but I would prefer to do it in php because the rest of the web app (a social network platform) is php. What I'm trying to do is leverage the power of html5 to remove all use of plugins. I hate browser plugins with a passion. Probably from my days running ppc linux where there were none so any site that required them was broken, but hell, I even hate dependence upon them in Windows. To keep everything server side php is why I'm seeking a php capable http server that does not have the same persistent connection limitations of Apache.
  5. Apache runs out of threads. It just can not maintain that many simultaneous connections. The point of Server Sent Events is that the web server can send messages to the browser without the browser needing to request them. If the connection is broken, the browser re-connects with the ID of last message it received so that it can get any messages it missed. It allows web applications that need server push capabilities to work without using flash or java - and without frequent polling that can be very hard on the server. I don't know if nginx is an option or not, I've not used it.
  6. Working on a web application involving server sent events. Apache is not good for this because of the persistent connections. node.js is awesome for this - but it's Javascript. I like postgresql (which I prefer to interface with via PDO), I like php, I like to keep the server side of things all in one language if I can. I've found node.js interface to MySQL but it really looks like node.js database layers are bolt on and not that mature yet. Is there a good web server for maintaining lots of connections that runs php?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.