Author Topic: ID Lookup  (Read 8446 times)

That's only the history for connect clients.
no, it isn't
The code you posted has nothing to do with this, and does only work for people with an rtb connect profile.

edit: fixed fail double quote
Just copy/paste RTB code to make another TCP object do the same thing that connect client does, but with less features


You're so dumb
You know what, forget you marble man. I won't bother to go into detail, but I seem to remember a time when you were a little stuffhead dropping stupid questions in coding help.
Did people insult you for being stupid? Yes. Yes, there were those who insulted you, but do you realize just how loving stupid and imbecilic and rude they looked? Apparently not, but I can show you: check a loving mirror.

You're lowering yourself to incredibly stuffty grounds.

Not only that, but you're giving him stuffty advice! Remember how I once told you your code was stuff? It wasn't. It was good code. I'm not even joking, I checked it over and it was good. (That's saying something if I'm complimenting your code: I was taught by Jetz and he was brown town-retentive about that stuff)

It seems that you've crashed again, though.

Now leave this topic and stop trolling with your broken code, insults, and sheer dumbassery.


Nice add-on, Zapk. I don't know why it hasn't been done before.

PS: you're right

something like this should work


//psuedo psuedocode (been working with javascript so this'll be wrong somehow)

function sendstuff(%name) {
%request = "cmd=search&query=" @ %name;
%tcp = new tcpobject;
%tcp.send("POST list.php HTTP/1.1\r\nHost: forum.returntoblockland.com\r\nContent-Type: application/x-www-form-urlencoded\r\nContent-Length:" @ strLen(%request); @ "\r\n" @ %request @ "\r\n\r\n");

// %tcp::onLine stuff to parse resulting data
function tcpObject::onLine(%data) {
echo(%data);
}

except with actual code that works. it's very similar to httpobjects except you have to send raw data instead of just "httpobject::get"
« Last Edit: August 29, 2013, 11:19:57 PM by Lugnut »

You know what, forget you marble man. I won't bother to go into detail, but I seem to remember a time when you were a little stuffhead dropping stupid questions in coding help.
Did people insult you for being stupid? Yes. Yes, there were those who insulted you, but do you realize just how loving stupid and imbecilic and rude they looked? Apparently not, but I can show you: check a loving mirror.

You're lowering yourself to incredibly stuffty grounds.

Not only that, but you're giving him stuffty advice! Remember how I once told you your code was stuff? It wasn't. It was good code. I'm not even joking, I checked it over and it was good. (That's saying something if I'm complimenting your code: I was taught by Jetz and he was brown town-retentive about that stuff)

It seems that you've crashed again, though.

Now leave this topic and stop trolling with your broken code, insults, and sheer dumbassery.
Basically my exact thoughts.

Nice add-on, Zapk. I don't know why it hasn't been done before.

PS: you're right

something like this should work


//psuedo psuedocode (been working with javascript so this'll be wrong somehow)

function sendstuff(%name) {
%request = "cmd=search&query=" @ %name;
%tcp = new tcpobject;
%tcp.send("POST list.php HTTP/1.1\r\nHost: forum.returntoblockland.com\r\nContent-Type: application/x-www-form-urlencoded\r\nContent-Length:" @ strLen(%request); @ "\r\n" @ %request @ "\r\n\r\n");

// %tcp::onLine stuff to parse resulting data
function tcpObject::onLine(%data) {
echo(%data);
}

except with actual code that works. it's very similar to httpobjects except you have to send raw data instead of just "httpobject::get"
Yeah, that's the code I have right now already, but there are actually two forms called "query" and the second one is for names.

Yeah, that's the code I have right now already, but there are actually two forms called "query" and the second one is for names.

So the above only returns results for ID input?

Also, forgot to say in my first post - great job with the GUI :)

So the above only returns results for ID input?

Also, forgot to say in my first post - great job with the GUI :)
I'm not sure. It doesn't seem to work with either, probably because there are two.