Not included in Quicklisp about de.setf.amqp HOT 18 CLOSED

I join this issue

from de.setf.amqp.

as my primary use is in production, the path through quick lisp adds no benefit and, as such, there has been no motivation to go through the process with this and the libraries on which it depends.

please, feel free to do whatever is necessary to include it and let me know.

from de.setf.amqp.

I tried to do it, but ran into problems when connecting libraries com.b9.puri.ppcre. It parses the connection string is incorrect. I ask you actual for for this project version of the library, if it is available

from de.setf.amqp.

On 16 Apr 2014, at 12:52, Rigidus [email protected] wrote:

I tried to do it, but ran into problems when connecting libraries com.b9.puri.ppcre. It parses the connection string is incorrect.

i do not understand, what you mean with “connection string”, do you mean the system name?

I ask you actual for for this project version of the library, if it is available

the code which i build with constantly is in the respective project in this account.
i last pulled it sometime this morning.
—
Reply to this email directly or view it on GitHub.

james anderson | [email protected] | http://dydra.com

from de.setf.amqp.

I pulled:
amqp-1-1-0-8-0
amqp-1-1-0-9-0
amqp-1-1-0-9-1
com.b9.puri.ppcre
de.setf.amqp
de.setf.codecs
de.setf.mime
de.setf.utility
..and made a few changes for built with quicklisp

When I try eval (defparameter c (make-instance 'amqp:connection :uri "amqp://guest:guest@localhost/"))

error occurs: port is not a number: GUEST@LOCALHOST.
in com.b9.puri:parse-uri

I tried to change the code inside com.b9.puri and it seemed to me that de.setf.amqp wants to have another version of the library

from de.setf.amqp.

i do not yet follow what is different in your build. i build with immediate pulls from the repository

/development/source/library/com/b9/puri$ git remote show origin
* remote origin
  Fetch URL: [email protected]:lisp/com.b9.puri.ppcre.git
  Push  URL: [email protected]:lisp/com.b9.puri.ppcre.git
  HEAD branch: master
/development/source/library/com/b9/puri$ git status
# On branch master
nothing to commit (working directory clean)

with a the result which performs as follows:

> (inspect (puri:uri "amqp://guest:guest@localhost/"))
 #<ORG.DATAGRAPH.SPOCQ.IMPLEMENTATION::REPOSITORY-METADATA {10210AC111}>) 
The object is a STANDARD-OBJECT of type PURI:URI.
0. SCHEME: :AMQP
1. HOST: "localhost"
2. PORT: NIL
3. PATH: "/"
4. QUERY: NIL
5. FRAGMENT: NIL
6. PLIST: (PURI::USERINFO "guest:guest")
7. ESCAPED: NIL
8. STRING: "amqp://guest:guest@localhost/"
9. PARSED-PATH: NIL
10. HASHCODE: NIL

which i understand to be correct. in production, with this code, we use uri with similar form - just without the trailing "/".

from de.setf.amqp.

I'm sorry, the problems were caused by my crooked hands :) Now I was able to run all the systems through quicklisp.

Now I have difficulty with the system rabbito. Some features I find in other packages. Relevant whether this system?

from de.setf.amqp.

/s/rabbito/rabbitmq

from de.setf.amqp.

good evening;

On 16 Apr 2014, at 16:48, Rigidus [email protected] wrote:

I'm sorry, the problems were caused by my crooked hands :) Now I was able to run all the systems through quicklisp.

Now I have difficulty with the system rabbito. Some features I find in other packages. Relevant whether this system?

rabbitio was just demonstration code.
i have never taken it anywhere near production.
—
Reply to this email directly or view it on GitHub.

from de.setf.amqp.

Good day :) Thank you! And if not a secret what is used in production?

from de.setf.amqp.

good afternoon,

On 16 Apr 2014, at 17:06, Rigidus [email protected] wrote:

Good day :) Thank you! And if not a secret what is used in production?

http://www.dydra.com has been running this code with a rabbitmq broker for several years.
with rmq at version : {rabbit,"RabbitMQ","2.8.4”}, i believe, it uses the 1-1-0-9-1 version protocol.

best regards, from berlin,

from de.setf.amqp.

Eh, I'd give to see this code :) At least send / receive messages :)
Best regards, from Saint-Petersburg, Russia

from de.setf.amqp.

On 16 Apr 2014, at 17:19, Rigidus [email protected] wrote:

Eh, I'd give to see this code :) At least send / receive messages :)

i am not sure what you mean?
the broker side is exactly the github code and the server side is nothing more than the streaming examples, just lots of them simultaneously with somewhat more error handling.
?

Best regards, from Saint-Petersburg, Russia

—
Reply to this email directly or view it on GitHub.

from de.setf.amqp.

I just want to create a working example, and that its inclusion in quicklisp that the community could use this library

from de.setf.amqp.

good afternoon,

On 16 Apr 2014, at 17:33, Rigidus [email protected] wrote:

I just want to create a working example, and that its inclusion in quicklisp that the community could use this library

look in the readmes directory.

—
Reply to this email directly or view it on GitHub.

from de.setf.amqp.

I try eval this example:

(defparameter d (make-instance 'amqp:connection :uri "amqp://guest:guest@localhost/"))
(amqp:with-open-channel (output d :exchange "ex" :type "direct" :queue "q3")
(format output "~a, ~a, a%"
(lisp-implementation-type)
(lisp-implementation-version)
amqp.u:version))

... and get an error:

end of file on #<AMQP-1-1-0-9-1:CHANNEL [#<PURI:URI amqp://localhost/>].1 {10073EFAF3}>
[Condition of type END-OF-FILE]

Backtrace: https://gist.github.com/rigidus/10970256

However, I see that the queue is created, although it 0 messages.

Maybe I made a mistake when passing parameters?

from de.setf.amqp.

Good morning!
James, I was not able to solve the problem. But I probably could get the
boss to pay for your work. On what amount can we talk?

2014-04-16 19:44 GMT+04:00 james anderson [email protected]:

good afternoon,

On 16 Apr 2014, at 17:33, Rigidus [email protected] wrote:

I just want to create a working example, and that its inclusion in
quicklisp that the community could use this library

look in the readmes directory.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-40614960
.

from de.setf.amqp.

as noted 16.4, the problem is not with this system.

from de.setf.amqp.