Friday, March 18. 2011Javascript delayingIn need of executing Javascript after the page has loaded, or something else has been initialized I came up with a simple but useful tiny "Delayer":
It can be initialized the following way:
Then you push your work the usual way:
Monday, March 14. 2011courier imap, authdaemond and vpopmails vchkpwA few years ago, it was possible to have courier-imap update the open-smtp relay file with it's authvchkpw module. This feature and thus imap-before-smtp disappeared with the introduction of courier-authdaemond because the vchkpw code of authdaemond does not have a chance to see the TCPREMOTEIP environment variable. I more or less lived with that, until a friend of mine got a new iphone... well yeah, one of those i-geeks, and that gadget apparently only supports imap, no pop. To re-enable imap-before-smtp I wrote a little setuid wrapper, calling vpopmails open_smtp_relay(). This wrapper has to replace the imapd command in your courier-imap startup script and will exec imapd, after opening the smtp relay, wile imap-login is still in place to authenticate via authdaemond's vchkpw module.
So while this worked to my satisfaction, I noticed that the tcp.smtp.cdb not always contained the IPs of the open-smtp file:
I also found out that, while the vpopmail FAQ is claiming that clearopensmtp is requesting locks on the open-smtp(.lock) file, the source does not read like it would.
It's not the prettiest piece of code, but it helps. Monday, May 10. 2010WebSockets Handshake non HTTP conforming?Update: Just found a revelatory discussion. The summary of Bjoern Hoehrmann is especially interesting with regards to that topic. While skimming through the new HTML5 WebSocket draft, I noticed the following exemplar HTTP message demonstrating the client message of a WebSocket handshake:
To me this looks non conforming to the HTTP spec due to the lack of an indicator that the request contains a message body. Quoting the 4th paragraph of section 4.3 of RFC2616: The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field in the request's message-headers. A message-body MUST NOT be included in a request if the specification of the request method (section 5.1.1) does not allow sending an entity-body in requests. A server SHOULD read and forward a message-body on any request; if the request method does not include defined semantics for an entity-body, then the message-body SHOULD be ignored when handling the request. Huh? Monday, April 20. 2009Looking for PHP Geeks in AustriaYou guessed. I'm desperately looking for decent PHP Coders in Vienna, Austria. The job posting (in german) can be found here: Just ping me if you're interested in an face-to-face interview. Friday, April 10. 2009PHP commandline highlighterJust chewed up a command line highlighter for php code. Cheers-
(Page 1 of 15, totaling 71 entries)
» next page
|
CategoriesRumbling PlanetInterview with Mage+ creator - Mayflower Blog - PHP
Wednesday, May 16. 2012 Composer Dependency Woes - blog.phpdeveloper.org » PHP Tuesday, May 15. 2012 Some throttling for PECL/mysqlnd_ms 1.4 - Ulf Wendel Tuesday, May 15. 2012 My Fresh MeatSyndicate Me© 2005 |




