Re: D web apps: cgi.d now supports scgi
+1 for scgi support :) On Sunday, 25 March 2012 at 04:43:07 UTC, Adam D. Ruppe wrote: https://github.com/adamdruppe/misc-stuff-including-D-programming-language-web-stuff some docs: http://arsdnet.net/web.d/cgi.html http://arsdnet.net/web.d/cgi.d.html The file cgi.d in there is my base library for web apps. Previously, it spoke regular CGI, FastCGI (with help from a C lib) and HTTP (with help from the netman.d and httpd.d files in that github). Now, in addition to those options, it also speaks SCGI - all by itself - and it can speak http without needing helper modules. The new embedded http server should work on all platforms too, not just linux like the old one, but I haven't tested it yet. This finishes out all the major web app interfaces that I'm aware of. To use them, you write your app with a GenericMain and always communicate through the Cgi object it passes you. === import arsd.cgi; void hello(Cgi cgi) { cgi.write(Hello, world! ~ cgi.request(name) ~ \n); } mixin GenericMain!hello; === And then compile: dmd hello.d arsd/cgi.d # builds a CGI binary dmd hello.d arsd/cgi.d -version=fastcgi # FastCGI. needs libfcgi C lib dmd hello.d arsd/cgi.d -version=scgi # SCGI dmd hello.d arsd/cgi.d -version=embedded_httpd # built-in http server The API is the same with all four options. With cgi or fastcgi, you put the binary where your web server can run it. With scgi and embedded_httpd, you run the binary. It persists as an application server. On the command line, you can say use the option --port 5000 for example to change the listening tcp port. The default for httpd right now is 8085. The default for scgi is 4000. Well, I don't have much else to say, but since it now does all four of the big interfaces easily, I thought I'd say something here. If you're interested in web programming with D, this will lay the foundation for you.
Re: avgtime - Small D util for your everyday benchmarking needs
Andrei Alexandrescu wrote: Wait, doesn't a benchmark always measure an algorithm with the same input? The fact that you formulate as a question indicates that you are unsure about the wright answer---me too, but 1) surely one can define a benchmark to have this property. But if one uses this definition, the used input would belong to the benchmark as a description. I have never seen a description of a benchmark including the input, but because I am more interested in theory I may have simply missed such descriptions. 2) if a probilistic algorithms is used, the meaning of input becomes unclear, because the state of the machine influences T. 3) if a heuristic is used by the benchmarked algorithm, then a made up family of benchmarks can prove T= O(n*n) for quick sort. -manfred
Re: D web apps: cgi.d now supports scgi
Thanks for doing this (and the other misc stuff) I wonder how can I generate unique, non predictable session ids.
Re: D web apps: cgi.d now supports scgi
On Sunday, 25 March 2012 at 19:14:32 UTC, dnewbie wrote: I wonder how can I generate unique, non predictable session ids. In web.d, there's a Session class that generates them with std.random.uniform. I suspect this isn't the best possible, but it's worked pretty well so far. The session class also uses a file to store persistent string key/value data.
Re: D web apps: cgi.d now supports scgi
On Sunday, 25 March 2012 at 19:22:02 UTC, Adam D. Ruppe wrote: On Sunday, 25 March 2012 at 19:14:32 UTC, dnewbie wrote: I wonder how can I generate unique, non predictable session ids. In web.d, there's a Session class that generates them with std.random.uniform. I suspect this isn't the best possible, but it's worked pretty well so far. The session class also uses a file to store persistent string key/value data. This is what I was looking for. Rock'n'roll!!
Re: D web apps: cgi.d now supports scgi
I can't compile web.d Notice: As of Phobos 2.055, std.date and std.dateparse have been deprecated. They will be removed in February 2012. Please use std.datetime instead. arsd\web.d(2671): Error: function std.date.dateFromTime is deprecated arsd\web.d(2672): Error: function std.date.yearFromTime is deprecated arsd\web.d(2673): Error: function std.date.monthFromTime is deprecated
Re: D web apps: cgi.d now supports scgi
On 26 March 2012 08:37, dnewbie r...@myopera.com wrote: On Sunday, 25 March 2012 at 19:22:02 UTC, Adam D. Ruppe wrote: On Sunday, 25 March 2012 at 19:14:32 UTC, dnewbie wrote: I wonder how can I generate unique, non predictable session ids. In web.d, there's a Session class that generates them with std.random.uniform. I suspect this isn't the best possible, but it's worked pretty well so far. The session class also uses a file to store persistent string key/value data. This is what I was looking for. Rock'n'roll!! Slightly off-topic, but what is your policy of derivative works Adam? So if I built something similar off your work, but gave you credit, and pushed any changes/bugfixes/improvements back to you, that would be ok? Basically, if I build my own libraries off yours, I assume that fine. Since I don't really want to repeat all the work you have done already. -- James Miller
Re: D web apps: cgi.d now supports scgi
On Sunday, 25 March 2012 at 20:12:16 UTC, dnewbie wrote: I can't compile web.d Oh yeah, Phobos loves removing perfectly good functionality. Just open the file and comment out that function. Make it simply: string date(string replacement, string[], in Element, string) { /* auto date = to!long(replacement); import std.date; auto day = dateFromTime(date); auto year = yearFromTime(date); auto month = monthNames[monthFromTime(date)]; replacement = format(%s %d, %d, month, day, year); */ return replacement; } and it will be fine. That function isn't really needed, it is just one of the template formatting options. Eventually, I'll port it to the monster that is std.datetime but I'm not in a big rush.
Re: D web apps: cgi.d now supports scgi
On Sunday, 25 March 2012 at 20:18:51 UTC, James Miller wrote: Slightly off-topic, but what is your policy of derivative works Adam? I don't really care; you can do whatever you want with it. It is generally Boost license like Phobos (I put it at the bottom of the files since licenses annoy me) which is pretty permissive. and pushed any changes/bugfixes/improvements back to you, that would be ok? Yea. And if your new functions might be generally useful or mix right it, feel free to do a pull request for that too. It is a misc stuff repo :P
Re: D web apps: cgi.d now supports scgi
On Sunday, 25 March 2012 at 19:37:12 UTC, dnewbie wrote: This is what I was looking for. Rock'n'roll!! BTW I tried to keep Session simple, and there's some doc comments, but the basic usage is as simple as: // loads the session, or creates a new one if needed auto session = new Session(cgi); // it does NOT auto save, so you want to call // session.commit() when you're done. // scope(exit) makes that easy. scope(exit) session.commit(); bool checkLogin() { if(session.hasKey(user_id)) { // see if a key is set // the user is logged in string uid = session.user_id; // can get data via opDispatch return true; } return false; } void logout() { session.invalidate(); // clears and deletes the session } void login() { session.invalidate(); // kill the guest session session.user_id = uid; // save the user id in the session via opDispatch } If you use web.d's FancyMain, it creates a session for you, so your ApiProvider class already has a session member you can tap right into. import web.d; class MySite : ApiProvider { void something () { session.cool = something; // works } } mixin FancyMain!MySite;
Re: D web apps: cgi.d now supports scgi
On 26 March 2012 09:28, Adam D. Ruppe destructiona...@gmail.com wrote: I don't really care; you can do whatever you want with it. I figured, but its nice to ask first :D. -- James Miller
Re: D web apps: cgi.d now supports scgi
On Sunday, 25 March 2012 at 19:22:02 UTC, Adam D. Ruppe wrote: On Sunday, 25 March 2012 at 19:14:32 UTC, dnewbie wrote: I wonder how can I generate unique, non predictable session ids. In web.d, there's a Session class that generates them with std.random.uniform. I suspect this isn't the best possible, but it's worked pretty well so far. The session class also uses a file to store persistent string key/value data. While using std.random is probably good enough for most sites, it's definitely worth keeping in mind that these session IDs are far from non-predictable. Generally, a secure random number generator is used instead, but Phobos lacks something like this.