<stellar-slack>
<hikarukusaka> Hello! we have original wallet service developed with php. we'd like to send request to HorizonAPI from curl. The problem we are facing is, how we can issue IOU(non-native) by sending request to HorizonAPI from curl? we used to do same thing with old stellar API and stellar.txt.
<stellar-slack>
<jed> to create transactions you need to use some client library. there are ones for JS, java,ruby,python, and go right now
[0__0] has quit [Remote host closed the connection]
[0__0] has joined #stellar-dev
[0__0] has quit [Remote host closed the connection]
[0__0] has joined #stellar-dev
<stellar-slack>
<hikarukusaka> as here (https://github.com/stellar/horizon/tree/master/docs) it says "You can interact directly with horizon via curl or a web browser but SDF provides a JavaScript SDK for clients to use to interact with Horizon." we'd like to directly send request via curl command.
<stellar-slack>
<sacarlson> hikarukusaka: you still need a lib to create the envelope packages to send to horizon that are crypto signed on the user side for security. this can be done in several ways from a browser or server using available libs in js, ruby and other
<stellar-slack>
<sacarlson> if you want to cancel the benefits of the security that this provides you could setup a server gateway that only requires curl interaction
<stellar-slack>
<sacarlson> but I think that would be a mistake
<stellar-slack>
<dzham> if it makes it easier, why not? set up a proxy on localhost, and talk to that through curl in php
<stellar-slack>
<sacarlson> what's on the localhost side? stellar-core?
<stellar-slack>
<dzham> js-stellar-sdk
<stellar-slack>
<sacarlson> if they are running js-stellar-sdk then why not on the user browser side?
<stellar-slack>
<dzham> yeah, good Q.. gateway maybe?
<stellar-slack>
<dzham> @sacarlson: you were doing something with browserify before? how was that experience?
<stellar-slack>
<sacarlson> I could add the feature of transactons without signing to mss-server to do such but don't think it's needed
<stellar-slack>
<dzham> I’m doing a library on top of js-stellar-sdk, with webpack, but something parses wrong :S
<stellar-slack>
<dzham> well, either it’s webpack, or it’s the javascript merging/minification used in `yo angular`’s default grunt script
<stellar-slack>
<dzham> Ok… I want’t to package my stuff + js-stellar-sdk into one
<stellar-slack>
<sacarlson> I just have my code in another js file and tap the libs of sdk and others
<stellar-slack>
<sacarlson> what's the advantage of repackaging?
<stellar-slack>
<dzham> one javascript file
<stellar-slack>
<dzham> it uses stellar but doesn’t expose it
<stellar-slack>
<sacarlson> how is one javascript file an advantage? other than making it imposible for someone to expose unknown problems
<stellar-slack>
<hikarukusaka> @sacarlson: we developed php base app so that is why I am thinking how we can send request to HorizonAPI via curl. otherwise we need to rebuild our app...
<stellar-slack>
<dzham> @sacarlsson: yeah, those are valid arguments :S
<stellar-slack>
<sacarlson> hikarukusaka: yes I understand it would require added effort as it's so different
<stellar-slack>
<dzham> ease-of-use, I’d say is the biggest benefit.. You can just get the library.min.js and include that in your project.
<stellar-slack>
<dzham> same as with js-stellar-sdk really.. they could have gone the route of using bower dependencies for all their deps
<stellar-slack>
<sacarlson> what features does your package add?
<stellar-slack>
<dzham> it’s a bit hush-hush right now.. but it’s an application on top of stellar
<stellar-slack>
<sacarlson> oh it's a complete package app or site rather than just a alternate lib
<stellar-slack>
<dzham> the former
<stellar-slack>
<sacarlson> not much difference bettween an app and a site anymore with js
``rawr has joined #stellar-dev
<stellar-slack>
<sacarlson> hikarukusaka: it is also posible for you to add javascripts inside php code to perform simple payments as I assume that's what you want to do
<stellar-slack>
<sacarlson> I think that would be cool to have. I might write one
<stellar-slack>
<sacarlson> you would still need something like mss-server or horizon to be used on the server side to detect payments being made by customers
<stellar-slack>
<sacarlson> getting the status of payments on accounts doesn't require signing and can be done with simple curl operations on the server side
de_henne has joined #stellar-dev
<stellar-slack>
<thanh> @dzham: is there a soft estimation on when will you app be ready for beta tester?
nivah has joined #stellar-dev
<stellar-slack>
<dzham> I’ve given up on estimates
nivah has quit [Ping timeout: 260 seconds]
nivah has joined #stellar-dev
Kwelstr` has quit [Ping timeout: 276 seconds]
Kwelstr` has joined #stellar-dev
``rawr has quit [Quit: Connection closed for inactivity]
stellar-slack1 has joined #stellar-dev
stellar-slack has quit [Ping timeout: 260 seconds]
nivah has quit [Ping timeout: 260 seconds]
etrepum has quit []
etrepum has joined #stellar-dev
mindstyle has joined #stellar-dev
mindstyle has quit [Ping timeout: 246 seconds]
mindstyle has joined #stellar-dev
<stellar-slack1>
<monsieurnicolas> Also one thing to consider is that there is no curl api to stellar-core to query the past, ie you can not know if a transaction made it into a ledger. There was some discussion before on this channel on building some sort of micro-horizon but the use case for it is very constrained resources (like you want to run on a Rasberry Pi Zero or something); for migrating apps from old -> new, the easiest
<stellar-slack1>
your language you're just hitting APIs, so the fact that it's implemented in c++, go and ruby should not matter).
<stellar-slack1>
<sacarlson> the mss-server I wrote is much like the micro-horizon we spoke of. it can read ledger transactions