Results 1 ... 104 found in trilema for 'hunchen'
spyked: and in other news: Hunchentoot tree updated with a sbcl distribution. ty diana_coman and bvt for the help!
mircea_popescu: there's 0 reason we even need to give a shit about hunchenbacktoot / rest of heathen world. people pay thousands/month to lease space in "seattle tech incubator", it's ~free here.
feedbot: http://thetarpit.org/posts/y06/09f-hunchentoot-genesis.html << The Tar Pit -- Hunchentoot genesis
snsabot: Logged on 2019-09-06 06:50:37 mircea_popescu: (this, also, before we get into "Hunchentoot talks with its front-end or with the client over TCP/IP sockets and optionally uses multiprocessing to handle several requests at the same time. Therefore, it cannot be implemented completely in portable Common Lisp. It currently works with LispWorks and all Lisps which are supported by the compatibility layers usocket and Bordeaux Threads." discussions.)
spyked: in any case, I'll publish the hunchentoot genesis today, as promised. /me bbl again
snsabot: Logged on 2019-09-06 04:29:51 spyked: http://logs.ossasepia.com/log/trilema/2019-09-05#1933935 <-- not entirely. at this point, http://logs.ossasepia.com/log/trilema/2019-09-05#1933934 is in the phase where "let's use these pieces we've reviewed to do some useful X", where X can be blogotron comments, logotron frontend, etc. so say I illustrate Hunchentoot through these applications; are they to be just for didactic purpose? and if yes, then w
spyked: other than that, I guess you meant "recent comments"? recent posts are on the main page; and as for title-urls, http://logs.nosuchlabs.com/log-search?q=from%3Afeedbot+hunchentoot&chan=trilema works from what I see
spyked: http://logs.ossasepia.com/log/trilema/2019-09-06#1934020 <-- there's no "conclusion" post, but yeah, these oughta go somewhere. the closest thing to a conclusion is http://thetarpit.org/posts/y06/09d-hunchentoot-vib.html#selection-970.0-970.7
mircea_popescu: also in the lulz, "Hunchentoot does not come with code to help with running it on a privileged port (i.e. port 80 or 443) on Unix-like operating systems. Modern Unix-like systems have specific, non-portable ways to allow non-root users to listen to privileged ports, so including such functionality in Hunchentoot was considered unnecessary. Please refer to online resources for help. At the time of this writing, [http://yaws
mircea_popescu: "Hunchentoot is (or was) for example used by <a href="http://quickhoney.com/">QuickHoney</a>, <a href="http://www.city-farming.de/">City Farming</a>, <a href="http://heikestephan.de/">Heike Stephan</a>." << forgot to put that lulz in the log somehow.
mircea_popescu: (this, also, before we get into "Hunchentoot talks with its front-end or with the client over TCP/IP sockets and optionally uses multiprocessing to handle several requests at the same time. Therefore, it cannot be implemented completely in portable Common Lisp. It currently works with LispWorks and all Lisps which are supported by the compatibility layers usocket and Bordeaux Threads." discussions.)
snsabot: Logged on 2019-09-06 04:29:51 spyked: http://logs.ossasepia.com/log/trilema/2019-09-05#1933935 <-- not entirely. at this point, http://logs.ossasepia.com/log/trilema/2019-09-05#1933934 is in the phase where "let's use these pieces we've reviewed to do some useful X", where X can be blogotron comments, logotron frontend, etc. so say I illustrate Hunchentoot through these applications; are they to be just for didactic purpose? and if yes, then w
spyked: http://logs.ossasepia.com/log/trilema/2019-09-05#1933935 <-- not entirely. at this point, http://logs.ossasepia.com/log/trilema/2019-09-05#1933934 is in the phase where "let's use these pieces we've reviewed to do some useful X", where X can be blogotron comments, logotron frontend, etc. so say I illustrate Hunchentoot through these applications; are they to be just for didactic purpose? and if yes, then w
asciilifeform would also like to hear the full hunchentoot vivisection .
feedbot: http://thetarpit.org/posts/y06/09d-hunchentoot-vib.html << The Tar Pit -- Hunchentoot: requests and replies [b]
snsabot: Logged on 2019-08-29 18:34:40 asciilifeform: saddest thing is, i'm not even certain it's more retarded than e.g. hunchentoot
spyked: tuff, which I suspect would make the result no different than either flask or hunchentoot
snsabot: Logged on 2019-08-29 18:34:40 asciilifeform: saddest thing is, i'm not even certain it's more retarded than e.g. hunchentoot
asciilifeform: saddest thing is, i'm not even certain it's more retarded than e.g. hunchentoot
spyked: http://logs.nosuchlabs.com/log/trilema/2019-08-25#1930885 <-- imho the right thing would be to eventually steal "everything". i'ma definitely do that for hunchentoot, tho I expect it'll take a while, given that I keep stumbling upon binaries and utfisms in these coads
feedbot: http://thetarpit.org/posts/y06/09c-hunchentoot-via.html << The Tar Pit -- Hunchentoot: requests and replies [a]
spyked: mircea_popescu, I completely agree. fwiw, I can genesis hunchentoot next thing if somebody asks for it. but would rather have the thing reviewed first, a propos of: http://logs.nosuchlabs.com/log/trilema/2019-08-22#1930229 . IMHO gotta document it, so that I don't make the same mistakes when I attempt a sane http replacement
spyked: mircea_popescu, yes, sorry for the confusion. the plan is to: post hunchentoot ep. 6 today, as per plan; and as september begins, post the plan for next month, which should include all the new things I'm working on (code, reviews of code, whatever arises in the meanwhile)
spyked: mircea_popescu, why should the output of weekly work be necessarily genesis? for now, it's a review of coad; the review will be followed by a genesis, as stated.
spyked: http://logs.nosuchlabs.com/log/trilema/2019-08-14#1928785 <-- ftr, just to make sure this isn't lost: this is the next item on my list after thetarpit commentz and hunchentoot genesis.
feedbot: http://thetarpit.org/posts/y06/09b-hunchentoot-v.html << The Tar Pit -- Hunchentoot: taskmaster code review
snsabot: Logged on 2019-08-11 16:20:54 spyked: http://logs.nosuchlabs.com/log/trilema/2019-08-09#1926869 <-- quite. and btw, to add to the hunchentoot thread, it can be easily adjusted while while running (hence my earlier change-class trick), so despite the ugly pythonesque systems code, it is lispy from a functional pov
spyked: http://logs.nosuchlabs.com/log/trilema/2019-08-09#1926869 <-- quite. and btw, to add to the hunchentoot thread, it can be easily adjusted while while running (hence my earlier change-class trick), so despite the ugly pythonesque systems code, it is lispy from a functional pov
asciilifeform: diana_coman: 'flask' is the py people's equiv. of 'hunchentoot'. eats the @app.route('/log/<chan>/<date>') etc sugars , does the 'html madlibs' thing on the 'templates' (a la 'cl-who') etc
snsabot: Logged on 2019-08-09 04:45:56 spyked: also, I guess there's also the fact that despite all its problems, there's a pile of CL code (e.g. hunchentoot, cl-irc) that works... very similarly to how wordpress does the job, despite its size and other warts. maybe Ada could also find similar pieces of code for Ada, but tbh I haven't looked... yet?
snsabot: Logged on 2019-08-09 04:45:56 spyked: also, I guess there's also the fact that despite all its problems, there's a pile of CL code (e.g. hunchentoot, cl-irc) that works... very similarly to how wordpress does the job, despite its size and other warts. maybe Ada could also find similar pieces of code for Ada, but tbh I haven't looked... yet?
spyked: also, I guess there's also the fact that despite all its problems, there's a pile of CL code (e.g. hunchentoot, cl-irc) that works... very similarly to how wordpress does the job, despite its size and other warts. maybe Ada could also find similar pieces of code for Ada, but tbh I haven't looked... yet?
asciilifeform: diana_coman: possibly CL, after spyked genesis's his cleaned up hunchen
asciilifeform: the www end does use 'flask', py's equiv of hunchentoot etc
asciilifeform: mp_en_viaje: hunchentoot is known to run on e.g. sbcl, ccl , where compiled.
asciilifeform: mp_en_viaje: at one time in '17 asciilifeform tried hand at writing basic ada www server. ended up burning it all. because ended up looking quite like 'hunchentoot', and quite evidently 'water took the shape of the bottle', i.e. inescapably
a111: Logged on 2019-08-01 15:40 asciilifeform: spyked: imho your 'hunchentoot' vivisection illustrates important point : just how much of the complexity of that thing is on acct of idjit tcpism's shit abstractions, i.e. the lengths to which it goes to pretend that the machines aint exchanging short packets in quasi-reliable ordering
asciilifeform: mp_en_viaje: i was only able to eat w/out choking because already, decade+ ago, had read 'hunchentoot' an' barfed
mp_en_viaje: why the fuck is this hunchenback even written in lisp ? it's pure python, why not just write it in python and be happy.
asciilifeform: ^ i.e. there are at least ~4~ successive impedance-mismatched layers of liquishit , if you count ~server~ (e.g. hunchentoot) . ~5~ if you count reader's browser !
asciilifeform: spyked: imho your 'hunchentoot' vivisection illustrates important point : just how much of the complexity of that thing is on acct of idjit tcpism's shit abstractions, i.e. the lengths to which it goes to pretend that the machines aint exchanging short packets in quasi-reliable ordering
feedbot: http://thetarpit.org/posts/y06/098-hunchentoot-iv.html << The Tar Pit -- Hunchentoot: acceptor code review
spyked: mp_en_viaje, answer'd: http://thetarpit.org/posts/y06/097-hunchentoot-iii.html#comment1
spyked: http://btcbase.org/log/2019-07-26#1925061 <-- yes indeed! the graphviz src file is at http://thetarpit.org/uploads/2019/07/hunchentootarch.dot , as linked from http://thetarpit.org/posts/y06/097-hunchentoot-iii.html#fn2
feedbot: http://thetarpit.org/posts/y06/097-hunchentoot-iii.html << The Tar Pit -- Hunchentoot: further architectural notes; and usage examples
spyked: many apologies for the prolonged feedbot downtime yesterday; I had to go offline the whole day on meat business and working through this week's hunchentoot layer-peeling
feedbot: http://thetarpit.org/posts/y05/096-hunchentoot-ii.html << The Tar Pit -- Notes on Hunchentoot architecture
spyked: http://btcbase.org/log/2019-06-22#1919220 <-- well, I can't in all good faith sign and publish the item before I understand it well enough to maintain it myself -- for the same money, I could just claim "use the version on shithub" and be done with that. I agree 100% that I should do small regular updates, but in this case breaking the thing into its constituent parts is the challenge, and "hunchentoot arc
spyked: http://btcbase.org/log/2019-06-22#1919157 <-- apologies for the lack of an update, I'm still neck-deep in hunchentoot study; I have a full draft of the monster ready in the workroom, but before publishing, I'm making sure I have a good understanding of the item, to avoid getting my ass bitten by unknown unknowns in the future
feedbot: http://thetarpit.org/posts/y05/093-hunchentoot-i.html << The Tar Pit -- A review of Hunchentoot's code history
a111: Logged on 2019-05-30 18:45 phf: http://btcbase.org/log/2019-05-29#1916136 << i'm using hunchentoot-1.2.35 but that's in no way explored, that's whatever i got out of quicklisp on first btcbase deploy
phf: i'm not sure that's particularly useful. at the time i was still switching between running btcbase on hunchentoot in prod and on alisp/aserve in development
phf: i'm also using http://marijnhaverbeke.nl/talks/defservice/ in front of it, and i added support for hunchentoot, so i rarely write anything that looks like hunchentoot specific code.
phf: http://btcbase.org/log/2019-05-29#1916136 << i'm using hunchentoot-1.2.35 but that's in no way explored, that's whatever i got out of quicklisp on first btcbase deploy
spyked: so far I've been looking at the project changelog and the patch history and the patches seem like a mixed bunch, with (perhaps) some useful things and breakage a la sslism. so before going further, I'd like to get some idea of what version of hunchentoot the lordship and the L2 are using
a111: Logged on 2019-05-22 21:36 lobbes: http://www.thetarpit.org/posts/y05/090-tmsr-work-ii.html#selection-197.31-205.258 << I wager there's a good chance you'll publish a genesis of tbnl/hunchentoot before I eat through mod_lisp, but I agree: as pieces emerge, we can sync up, regrind as needed, etc.
spyked: good morning, #t! following up on the http://btcbase.org/log/2019-05-22#1915244 thread: I've started reviewing hunchentoot, the first step would be to figure out which code base to use as a starting point from the genesis.
lobbes: http://www.thetarpit.org/posts/y05/090-tmsr-work-ii.html#selection-197.31-205.258 << I wager there's a good chance you'll publish a genesis of tbnl/hunchentoot before I eat through mod_lisp, but I agree: as pieces emerge, we can sync up, regrind as needed, etc.
spyked: mp_en_viaje, should take less than that, giving myself time to work through potential unexpected issues, e.g. it's been a while since last time I used hunchentoot, need to reload it in head.
spyked: http://btcbase.org/log/2019-05-06#1911562 <-- I will give hunchentoot a second look as well, in light of http://btcbase.org/log/2019-05-06#1911437
a111: Logged on 2019-05-06 15:00 phf: mp_en_viaje: it's the shitsoup ecosystem, there's a handful of packages smartly written, like hunchentoot or cl-http, and then there's new wave of cffi-everything approaches, that stand tall and pretend to be people
a111: Logged on 2019-05-06 15:01 phf: tbnl from which hunchentoot comes used to be pure mod_lisp, another code to look at
a111: Logged on 2019-05-06 15:00 phf: mp_en_viaje: it's the shitsoup ecosystem, there's a handful of packages smartly written, like hunchentoot or cl-http, and then there's new wave of cffi-everything approaches, that stand tall and pretend to be people
phf: tbnl from which hunchentoot comes used to be pure mod_lisp, another code to look at
asciilifeform: 'hunchentoot' etc. are almost always run 'behind' apache as it is ( so static files serve up faster )
phf: mp_en_viaje: it's the shitsoup ecosystem, there's a handful of packages smartly written, like hunchentoot or cl-http, and then there's new wave of cffi-everything approaches, that stand tall and pretend to be people
asciilifeform: http://btcbase.org/log/2019-05-06#1911347 << last time i surveyed the available items (~decade ago) 'hunchentoot' turned out to be the only 1 that wasn't fatally defective in some obvious way (some of the alternatives wouldn't build at all, others -- wouldn't use iron threads on x86; yet others missing some large piece , e.g. custom eggog pgs , etc ) but it's been a while
a111: Logged on 2019-05-06 09:23 spyked: http://btcbase.org/log/2019-05-02#1910755 <-- I dun much like hunchentoot, on account of http://thetarpit.org/posts/y03/05c-development-log-i.html#selection-187.0-192.0 ; but I'm open to using it if the alternatives turn out to be insufficient
phf: spyked: wookie is not a hunchentoot fork, it's its own thing built around an async ffi. one thing you might want to add to your list is how much ffi-ing is required, or rather how "c heavy" the code is. for example teepeedee2 is extremely fast, but doesn't work anywhere but sbcl and linux, because it uses all kinds of libc features.
spyked: http://btcbase.org/log/2019-05-02#1910755 <-- I dun much like hunchentoot, on account of http://thetarpit.org/posts/y03/05c-development-log-i.html#selection-187.0-192.0 ; but I'm open to using it if the alternatives turn out to be insufficient
a111: Logged on 2019-05-02 14:35 lobbes: though it seems like lots of people here use hunchentoot for that purpose, and it seems that hunchentoot is easily modified to interface with apache through mod_lisp
lobbes: though it seems like lots of people here use hunchentoot for that purpose, and it seems that hunchentoot is easily modified to interface with apache through mod_lisp
asciilifeform: you don't miss cgi in hunchentoot.
asciilifeform: trinque: that's exactly the kind of thing i wouldn't do. my hypothetical http serv would be strictly for fully adatronic app. like hunchentoot in cl world.
phf: amusingly none of that "super fast" shit is used anywhere. venerable hunchentoot was used used by weitz to deliver consulting solutions (was also used by me for same purpose back when it was tbnl), these super fast toys are used to host author's blog.
phf: ben_vulpes: are you using hunchentoot?
trinque: haha, but hey sbcl is threaded and hunchentoot exists.
phf: re cmucl threads i think that it doesn't always preempt correctly. like it has explicit yield, which you don't always have to call, but it being there implies. also hunchentoot wasn't working right without putting a yield somewhere in the scheduler. it's all very vague, because i've not spend any time looking at it
ben_vulpes: (hunchentoot uber alles)
phf: ben_vulpes: actually right now i'm heathen-ing it, by using quicklisp too. problem is btcbase depends on 35 different projects (like hunchentoot pulls 8 deps, cl-irc 2, etc.) so cmucl version i had all 35 hand patched to various degrees. the right way seems to be giving all those project the v treatment: pull them in, strip them of fluff, genesis, etc.
asciilifeform: afaik the lisp folks here are all using hunchentoot
trinque: plenty of lisp tools there too; I've used hunchentoot plenty
gribble: trinque was last seen in #trilema 3 hours, 55 minutes, and 40 seconds ago: <trinque> what www thinger do you use? hunchenfart?
phf: (a much harder task in hunchentoot)
phf: well, to be fair it's not very good, but it hosted cliki for 10 years, easier to hack on than hunchentoot on account of having simpler design and i'm trying to make it sling byte arrays
trinque: what www thinger do you use? hunchenfart?
trinque: hunchentoot uber alles
trinque: hunchentoot is good
asciilifeform: e.g., in a few years a n00b looking for 'web server' will find ten qeergendered flycheckesque atrocities and - if he is very very lucky - one 'hunchentoot' in a state of disrepair
assbot: Logged on 06-01-2016 04:07:24; phf: asciilifeform, ben_vulpes, adlai: edi weitz (cl-ppcre, hunchentoot, flexi-streams rest of ediware) published a book of common lisp recipes http://www.amazon.com/o/asin/1484211774
assbot: Logged on 06-01-2016 04:07:24; phf: asciilifeform, ben_vulpes, adlai: edi weitz (cl-ppcre, hunchentoot, flexi-streams rest of ediware) published a book of common lisp recipes http://www.amazon.com/o/asin/1484211774
phf: asciilifeform, ben_vulpes, adlai: edi weitz (cl-ppcre, hunchentoot, flexi-streams rest of ediware) published a book of common lisp recipes http://www.amazon.com/o/asin/1484211774
assbot: Logged on 26-07-2015 22:16:44; ben_vulpes: the "async" cl webserver the nodebros are banging on about blocks the repl when instantiated in a cl-async 'event loop', unlike how hunchentoot starts a server and then returns on threaded sbcl.
ben_vulpes: the "async" cl webserver the nodebros are banging on about blocks the repl when instantiated in a cl-async 'event loop', unlike how hunchentoot starts a server and then returns on threaded sbcl.
ben_vulpes: anyways i was poking at hunchentoot in service of making an httoy out of some of the patches that you've posted recently and discovered that the sbcl i had on the plane didn't support threads
gabriel_laddel: trinque: are you just playing around with hunchentoot, or writing a production system?
trinque: #<HUNCHENSOCKET:WEBSOCKET-ACCEPTOR (host *, port 8081)>
assbot: Logged on 10-07-2015 20:46:57; trinque: not bad, hunchentootin' today
trinque: it's somewhat interesting to note that wikipedia has a german page on hunchentoot, but the english one was deleted.
trinque: not bad, hunchentootin' today
trinque: hm, time to work on some hunchentootage
asciilifeform: trinque: even hunchentoot. the www stack is fundamentally retarded
trinque: even hunchentoot?