Re: XML-RPC WEBrick problem (error during method invocation)

On 10/06/2010 04:47 PM, Nikita Kuznetsov wrote:
> 
>>>
>>> I am completely stuck on this. All help would be greatly appreciated.
>> Since this is a school assignment, I'll only say that you're very close
>> to the solution and suggest that you closely watch the output of your
>> server while you run your client.
>>
> 
> 
> Well, the problem for me is that i already know i am close. I was 
> advised to try out some things like make a single class containing all 
> the things i needed. But the problem for me is syntax, i am completely 
> new to Ruby, so some simple framework guidelines would be great, im not 
> asking for the exact code, thats up to me to work out anyway, otherwise 
> this assignement is useless. Im just stuck in one of those moments where 
> i understand the parts but not the whole and i cant seem to put the 
> parts together. this may sound a little confusing but i think you 
> understand what i mean.

The problem is that you are so near to finding the solution to your
problem that to say much more would give you the answer.

> If you could just show me how to make a function to run a simple puts 
> from the server, i would be extremely happy. The output of my server is 
> usually the same, date+time of connection, that its a POST procedure and 
> that its http. Doesnt really tell me much.

Showing such an example would solve your problem entirely, don't you
think?  Please don't think I'm making light of your situation.  Once you
figure out the problem, you'll definitely have one of those palm-face
moments.

Look closer at that server output, and don't discount anything out of
hand.  It may help if you gather the server output generated during a
single run of your client and then identify what client action causes
each line of the server output to be displayed and what each line means.
 That's exactly what I did with your sample code (once I corrected the
server code to get something that replicates your issue) to figure out
what's going on.

I know it can be frustrating, but you can just get a certain kind of
blindness to what's going on with your code at times, and the only ways
out are to ask for help (if you can get it, sorry) or really attack your
problem from a different angle.  Sometimes it's even good to completely
ignore the code for a day or two and then come back to it with fresh
eyes.  I've used all of these techniques numerous times.

Above all, be persistent and have confidence that you will figure this out.

-Jeremy