[CfP] 2018 Scheme and Functional Programming Workshop
Greetings magnificent Clojurians! I'm writing to let you know that the 2018 Scheme and Functional Programming Workshop is now accepting submissions. In fact... there's just two weeks left! Submit your papers soon! Here's the Call for Papers: DEADLINE: 9 July 2018, (Any time in the world) WEBSITE: https://brinckerhoff.org/scheme2018/ LOCATION: St. Louis, MO, USA (co-located with ICFP and Strange Loop) DATE: 28 September 2018 (Friday) The 2018 Scheme and Functional Programming Workshop is calling for submissions. Full papers are due 9 July 2018. Authors will be notified by 20 July 2018. Camera-ready versions are due 9 September 2018. All deadlines are (23:59 UTC-12), "Anywhere on Earth". We invite high-quality papers about novel research results, lessons learned from practical experience in industrial or educational setting, and even new insights on old ideas. We welcome and encourage submissions that apply to any language that can be considered Scheme: from strict subsets of RnRS to other "Scheme" implementations, to Racket, to Lisp dialects including Clojure, Emacs Lisp, Common Lisp, to functional languages with continuations and/or macros (or extended to have them) such as Dylan, ECMAcript, Hop, Lua, Scala, Rust, etc. The elegance of the paper and the relevance of its topic to the interests of Schemers will matter more than the surface syntax of the examples used. Topics of interest include (but are not limited to): Interaction: program-development environments, debugging, testing, refactoring Implementation: interpreters, compilers, tools, garbage collectors, benchmarks Extension: macros, hygiene, domain-specific languages, reflection, and how such extension affects interaction. Expression: control, modularity, ad hoc and parametric polymorphism, types, aspects, ownership models, concurrency, distribution, parallelism, non-determinism, probabilism, and other programming paradigms Integration: build tools, deployment, interoperation with other languages and systems Formal semantics: Theory, analyses and transformations, partial evaluation Human Factors: Past, present and future history, evolution and sociology of the language Scheme, its standard and its dialects Education: approaches, experiences, curricula Applications: industrial uses of Scheme Scheme pearls: elegant, instructive uses of Scheme Submission Information Please submit full papers and experience reports to our Submission Page: https://easychair.org/conferences/?conf=scheme2018 [NEW SINCE 2017!] Paper submissions must use the format acmart and its sub-format acmlarge. They must be in PDF, printable in black and white on US Letter size. Microsoft Word and LaTeX templates for this format are available at: http://www.sigplan.org/Resources/Author/ This change is in line with ACM conferences (such as ICFP with which we are colocated) switching from their traditional two-column formats (e.g. sigplanconf) to the above. While a two-column format with small fonts is much more practical when reading printed papers, the single-column format with large fonts is nicer to view on a computer screen, as most papers are read these days. To encourage authors to submit their best work, we offer three tracks: * Full Papers, with a limit of 14 pages. Each accepted paper will be presented by its authors in a 25 minute slot including Q&A. * Experience Reports, with a limit to 14 pages. Each accepted report will be presented by its authors in a 25 minute slot including Q&A. * Lightning talks, with a limit to 192 words. Each accepted lightning talk will be presented by its authors in a 5 minute slot, followed by 5 minutes of Q&A. The size limits above exclude references and any optional appendices. There are no size limits on appendices, but the papers should stand without the need to read them, and reviewers are not required to read them. Authors are encouraged to publish any code associated to their papers under an open source license, so that reviewers may try the code and verify the claims. Proceedings will be printed as a Technical Report at the University of Alabama at Birmingham. Publication of a paper at this workshop is not intended to replace conference or journal publication, and does not preclude re-publication of a more complete or finished version of the paper at some later conference or in a journal. Sincerely, John Clements, General Chair William E. Byrd, Program Committee Chair Program Committee: Claire Alvis (Sparkfund, USA) William E. Byrd (Program Committee Chair) (University of Alabama at Birmingham, USA) Maxime Chevalier-Boisvert (Montreal Institute for Learning Algorithms, Canada) John Clements (General Chair) (Cal Poly, San Luis Obispo, USA) Ronald Garcia (University of British Columbia, Canada) Yukiyoshi Kameyama (University of Tsukuba, Japan) Paul A. Steckler (Northeastern University, USA) Larisse Voufo (Google, USA) Workshop Steering Co
Re: Clojure/flutter
On Thu, Apr 26, 2018, 10:08 AM Gregg Reynolds wrote: > > > On Wed, Apr 25, 2018 at 5:01 PM, Robert Levy wrote: > >> What would you say is the advantage of using Flutter instead of React >> Native? Assuming you're not interested in Dart, what is the selling point? >> > > I haven't used it yet > Ok, I have now used Flutter. In mild anger: wrapped a c lib. That took a little doing. But the UI was a breeze. And it's fast. (Android only). I'm completely sold. My guess is that it will quickly establish World Domination, or something very close to it. Technically it beats the snot out of the competition, imho. Dart is not the worst language in the world, but it ain't clojure. My advice to the Clojure community: jump on this sucker now. Get in while the getting's hot. There's not much I'd like better than writing a clojuredart engine, but I don't have the time or the chops, alas. But if it can be done for javascript why not dart? G -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: downloading of files from Dropbox using cli-http
That's the result:
curl -vX POST https://content.dropboxapi.com/2/files/download --header
'Authorization: Bearer QfCCK...' --header 'Dropbox-API-Arg:
{"path":"/log.txt"}'>x.txt
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0* Trying 2620:100:6022:8::a27d:4208...
* TCP_NODELAY set
* Connected to content.dropboxapi.com (2620:100:6022:8::a27d:4208) port 443
(#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [106 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3302 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Dropbox, Inc;
OU=Dropbox Ops; CN=content.dropboxapi.com
* start date: Feb 7 00:00:00 2017 GMT
* expire date: Feb 12 12:00:00 2020 GMT
* subjectAltName: host "content.dropboxapi.com" matched cert's
"content.dropboxapi.com"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High
Assurance Server CA
* SSL certificate verify ok.
> POST /2/files/download HTTP/1.1
> Host: content.dropboxapi.com
> User-Agent: curl/7.54.0
> Accept: */*
> Authorization: Bearer QfCCK...
> Dropbox-API-Arg: {"path":"/log.txt"}
>
0 00 00 0 0 0 --:--:-- 0:00:01 --:--:--
0< HTTP/1.1 200 OK
< Server: nginx
< Date: Mon, 25 Jun 2018 15:29:43 GMT
< Content-Type: application/octet-stream
< Content-Length: 199945
< Connection: keep-alive
< accept-ranges: bytes
< etag: W/"2a575a545945"
< pragma: no-cache
< cache-control: no-cache
< original-content-length: 199945
< dropbox-api-result: {"name": "log.txt", "path_lower": "/log.txt",
"path_display": "/log.txt", "id": "id:hNm0VDys4tAADA",
"client_modified": "2018-06-24T21:53:42Z", "server_modified":
"2018-06-24T21:53:43Z", "rev": "2a575a545945", "size": 199945,
"content_hash":
"4366a79928e7a4e7db9da0c7b05c4c76fa016c0f5886fa106b47fd2e7a960db9"}
< X-Server-Response-Time: 765
< X-Dropbox-Request-Id: 3301820ab86536937d476e8ea895ff22
< X-Robots-Tag: noindex, nofollow, noimageindex
<
{ [15632 bytes data]
100 195k 100 195k0 0 156k 0 0:00:01 0:00:01 --:--:--
156k
* Connection #0 to host content.dropboxapi.com left intact
The has been downloaded successfully.
Am Montag, 25. Juni 2018 17:09:58 UTC+2 schrieb Thomas:
>
> try and do a curl -v and see what it really does under the covers as there
> might be a redirect
>
> Good luck,
> Thomas
>
> On Monday, 25 June 2018 14:38:12 UTC+2, Johannes wrote:
>>
>> Hi,
>>
>> I am trying to download a file from Dropbox which I can get with the Http
>> request:
>>
>> POST /2/files/download Host: https://content.dropboxapi.com User-Agent:
>> api-explorer-client Authorization: Bearer QfCCK... Dropbox-API-Arg:
>> {"path":"/log.txt"}
>>
>> or the curl request looks like that:
>>
>> curl -X POST https://content.dropboxapi.com/2/files/download \ --header
>> 'Authorization:
>> Bearer QfCCK...' \ --header 'Dropbox-API-Arg: {"path":"/log.txt"}'
>>
>> If I try the following using cli-http in a Clojurescript repl:
>>
>> (go (let [response (> https://content/dropboxapi.com/2/files/download"; {:headers
>> {"authorization" "Bearer QfCCK..." "Dropbox-API-Arg"
>> "{\"path\":\"/log.txt\"}"} }))] (println response)))
>>
>> I get
>>
>> #object[*cljs.core.async.impl.channels.ManyToManyChannel*]
>>
>> {:status 0, :success false, :body , :headers {}, :trace-redirects [
>> https://content/dropboxapi.com/2/files/download
>> https://content/dropboxapi.com/2/files/download], :error-code
>> :http-error, :error-text [0]}
>>
>>
>> I cannot figure out where my mistake is. Any help?
>>
>>
>> Johannes
>>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
Re: downloading of files from Dropbox using cli-http
try and do a curl -v and see what it really does under the covers as there
might be a redirect
Good luck,
Thomas
On Monday, 25 June 2018 14:38:12 UTC+2, Johannes wrote:
>
> Hi,
>
> I am trying to download a file from Dropbox which I can get with the Http
> request:
>
> POST /2/files/download Host: https://content.dropboxapi.com User-Agent:
> api-explorer-client Authorization: Bearer QfCCK... Dropbox-API-Arg:
> {"path":"/log.txt"}
>
> or the curl request looks like that:
>
> curl -X POST https://content.dropboxapi.com/2/files/download \ --header
> 'Authorization:
> Bearer QfCCK...' \ --header 'Dropbox-API-Arg: {"path":"/log.txt"}'
>
> If I try the following using cli-http in a Clojurescript repl:
>
> (go (let [response ( https://content/dropboxapi.com/2/files/download"; {:headers
> {"authorization" "Bearer QfCCK..." "Dropbox-API-Arg"
> "{\"path\":\"/log.txt\"}"} }))] (println response)))
>
> I get
>
> #object[*cljs.core.async.impl.channels.ManyToManyChannel*]
>
> {:status 0, :success false, :body , :headers {}, :trace-redirects [
> https://content/dropboxapi.com/2/files/download
> https://content/dropboxapi.com/2/files/download], :error-code
> :http-error, :error-text [0]}
>
>
> I cannot figure out where my mistake is. Any help?
>
>
> Johannes
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
downloading of files from Dropbox using cli-http
Hi,
I am trying to download a file from Dropbox which I can get with the Http
request:
POST /2/files/download Host: https://content.dropboxapi.com User-Agent:
api-explorer-client Authorization: Bearer QfCCK... Dropbox-API-Arg:
{"path":"/log.txt"}
or the curl request looks like that:
curl -X POST https://content.dropboxapi.com/2/files/download \ --header
'Authorization:
Bearer QfCCK...' \ --header 'Dropbox-API-Arg: {"path":"/log.txt"}'
If I try the following using cli-http in a Clojurescript repl:
(go (let [response (https://content/dropboxapi.com/2/files/download"; {:headers
{"authorization" "Bearer QfCCK..." "Dropbox-API-Arg"
"{\"path\":\"/log.txt\"}"} }))] (println response)))
I get
#object[*cljs.core.async.impl.channels.ManyToManyChannel*]
{:status 0, :success false, :body , :headers {}, :trace-redirects
[https://content/dropboxapi.com/2/files/download
https://content/dropboxapi.com/2/files/download], :error-code :http-error,
:error-text [0]}
I cannot figure out where my mistake is. Any help?
Johannes
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
