SLICk - Small Lightweight multIcoin Client

gweedo

legendary

Activity: 1498

Merit: 1000

Quote from: kaoD on April 01, 2013, 01:47:43 AM

Quote from: gweedo on April 01, 2013, 01:23:43 AM

He is returning JSON cause doesn't understand the specification, just like you.

I don't know his intentions but I'm very sure I know about JSON-RPC. What you seem to be unable to understand is the fact that RPC is not tied to a specific standard.

http://en.wikipedia.org/wiki/Remote_procedure_call

"Many different (often incompatible) technologies can be used to implement the concept."

Why are you so focused in JSON-RPC? He didn't even mention it once.

I know what RPC is but you clearly don't put two and two together, he has JSON, and is talking about RPC which is a implementation really. You can't just call RPC. So he was trying to say JSON-RPC but instead was just calling it RPC. The more stuff you post the less and less your doing yourself of making you look like a bad programmer, I would say quiet now so I don't have to keep showing you up.

gweedo

legendary

Activity: 1498

Merit: 1000

Quote from: kaoD on April 01, 2013, 01:18:14 AM

Quote from: ?? on ??

Otherwise why is he returning JSON?

Because JSON is a handy object notation?

And you're right, it's Bitmessage the one that uses XML-RPC. Got both mixed up.

He is returning JSON cause doesn't understand the specification, just like you. JSON-RPC is so you can keep track of what methods your sending and what results your receiving so you know your executing on and incase any results or sending gets lost. Instead of just returning json for commands you don't know the order you sent them in.

transcoder

full member

Activity: 146

Merit: 100

The download link at http://virtualminer.eu/SlickSrc.7z appears to be broken. Do you have an updated link?

CryptoWallets.org

newbie

Activity: 38

Merit: 0

I'v been looking for something like this! Thank you

kaoD

newbie

Activity: 22

Merit: 0

Quote from: gweedo on April 01, 2013, 01:23:43 AM

He is returning JSON cause doesn't understand the specification, just like you.

I don't know his intentions but I'm very sure I know about JSON-RPC. What you seem to be unable (or worse, unwilling) to understand is the fact that RPC is not tied to a specific standard.

http://en.wikipedia.org/wiki/Remote_procedure_call

"Many different (often incompatible) technologies can be used to implement the concept."

Why are you so focused in JSON-RPC? He didn't even mention it once.

kaoD

newbie

Activity: 22

Merit: 0

Quote from: ?? on ??

Otherwise why is he returning JSON?

Because JSON is a handy object notation? I've done some RPC implementations which worked through JSON but weren't JSON-RPC compliant (mainly over RESTful services).

And you're right, it's Bitmessage the one that uses XML-RPC. Got both mixed up.

kaoD

newbie

Activity: 22

Merit: 0

Quote from: ?? on ??

No, I was going by http://json-rpc.org/wiki/specification and that specification wasn't found in the program, it was just JSON returns, no JSON-RPC returns.

Again, RPC is not JSON-RPC. If you can Call Procedures Remotely, it's RPC! Tongue

kaoD

newbie

Activity: 22

Merit: 0

Quote from: ?? on ??

This could be scary but you said you have created a lightweight RPC server bitcoind, based on JPosse, I just looked at that code, it isn't RPC, it just returns JSON, this would not work with any existing software, kinda disappointment I could have really used this.

RPC just means Remote Procedure Call so he wasn't lieing. You've probably confused RPC with XML-RPC which is the standard used in Bitcoin-QT.

crazy_rabbit

legendary

Activity: 1204

Merit: 1001

RUM AND CARROTS: A PIRATE LIFE FOR ME

Quote from: Nachtwind on February 12, 2013, 11:35:36 AM

...i forgot to upload the dependencies.. mea culpa. Doing that in a few min.

Did you have a chance to see the Terracoin DEV's update? I think it will solve the hash problem you were having.

Nachtwind

hero member

Activity: 700

Merit: 507

...i forgot to upload the dependencies.. mea culpa. Doing that in a few min.

Nachtwind

hero member

Activity: 700

Merit: 507

Uploading my current snapshot of sources. Due to a shortage on time i will just do this for the moment..

crazy_rabbit

legendary

Activity: 1204

Merit: 1001

RUM AND CARROTS: A PIRATE LIFE FOR ME

Looking forward to it though, gonna be exciting.

Nachtwind

hero member

Activity: 700

Merit: 507

sacko: Wie gesagt, - bitte hier englisch sprechen, dann haben alle was davon.
sacko: Like I said, please talk english here, so everyone can follow the discussion.

Sorry for the delay.. was not home for the weekend, and couldnt include TRC yet. Current list of whats to do till the release:

- including TRC
- fixing some minor "config" trouble (currently you call the program with the config file as parameter, yet some places in bitcoinJ need this parameter and cannot get it without too heavy modification.. and i want to avoid that)
- fixing some minor bugs

sacko

full member

Activity: 174

Merit: 253

Danke für die Info.

Achja: Es steht dir frei, die deutsche Sprache als hier fehlplatziert oder womöglich unangemessen zu betrachten, doch, solltest du deutsche Wurzeln haben, dann ... (du kennst meine Meinung)

Nachtwind

hero member

Activity: 700

Merit: 507

Quote from: ?? on ??

@Nachtwind
Gibt es einen client mit dem ich Litecoins empf/senden kann, ohne die ganze blockchain runterzuladen?

Translated: Is there a client that i can use for sending/receiving Litecoins without having to download the full blockchain

Not that i know. Even with SLICK you have to download the chain.

Translated: Soweit ich weis nicht, auch SLICK lädt die gesamte Blockchain runter. Achja, bitte deutschsprachige Nachrichten im entsprechenden Forum schreiben.

Nachtwind

hero member

Activity: 700

Merit: 507

Status update:
Currently adding TRC to it and putting some minor finishing touches to everything.

When that is done i am going to upload the source/jar files

crazy_rabbit

legendary

Activity: 1204

Merit: 1001

RUM AND CARROTS: A PIRATE LIFE FOR ME

Looking forward to it! :-)

Nachtwind

hero member

Activity: 700

Merit: 507

Quote from: Atruk on January 11, 2013, 02:35:53 PM

Quote from: Nachtwind on January 11, 2013, 02:23:35 PM

Quote from: Mike Hearn on January 11, 2013, 11:46:27 AM

You could try and merge some of the changes upstream, but honestly, I'm not sure I care about litecoin. Is there some massively compelling reason you want to support that?

Yes, because i intended the client to work with bitcoin and litecoin and virtually every other *coin that is available atm - but only worked out BTC and LTC so far Wink

Keep in mind that all of the altcoins have their own little wallet quirks that are going to require maintenance. Reciever files in DevCoin, Pay Per Share mining in PPCoin, tec.

Thats why i just included BTC and LTC so far.. i would like to tackle NMC next, but dont have the time right now.

Atruk

hero member

Activity: 700

Merit: 500

Quote from: Nachtwind on January 11, 2013, 02:23:35 PM

Quote from: Mike Hearn on January 11, 2013, 11:46:27 AM

You could try and merge some of the changes upstream, but honestly, I'm not sure I care about litecoin. Is there some massively compelling reason you want to support that?

Yes, because i intended the client to work with bitcoin and litecoin and virtually every other *coin that is available atm - but only worked out BTC and LTC so far Wink

Keep in mind that all of the altcoins have their own little wallet quirks that are going to require maintenance. Reciever files in DevCoin, Pay Per Share mining in PPCoin, tec.

Nachtwind

hero member

Activity: 700

Merit: 507

Quote from: Mike Hearn on January 11, 2013, 11:46:27 AM

You could try and merge some of the changes upstream, but honestly, I'm not sure I care about litecoin. Is there some massively compelling reason you want to support that?

Yes, because i intended the client to work with bitcoin and litecoin and virtually every other *coin that is available atm - but only worked out BTC and LTC so far Wink

Topic: SLICk - Small Lightweight multIcoin Client (Read 4628 times)