On Wed, 15 Jan 2003 14:23:18 -0500 Colin Viebrock <[EMAIL PROTECTED]> wrote:
I'm not either! LOL!Chris R Chapman wrote:I've communicated with Charles directly and understand what he needs-- andSo have I, and I'm still not sure what he needs that isn't provided already.
his frustration.
So lets all call a time-out so I can re-group and figure out what holes I still need to fill.
Yea but the issue still comes back to a *COMPLETE* example of *ALL* the stuff / layers that occur between the brian's desire to get a domain and getting OpenSRS to cough up that domain ....Technically, yes, but that's just for the XCP message itself. Charles isTrue, but *they* are given as examples in the API, but not in the
driving at what happens _before_ the XCP is sent, ie the handshaking and
preamble messages as per Appendix C. These aren't provided in the API as
examples-- however, if you're comfortable with PERL, these can be easily
discerned from the API instructions.
Appendix. CHECK_VERSION is in chapter 8.10, and AUTHENTICATE_USER is 8.4.
Please review my comment to date.You're right, you are paranoid. As per the latter, the API manual is, to beI agree, the API manual could use some tweaking (in fact, I suggested a
blunt, a work in progress. There are numerous errors and omissions, and if
I ever wrote something like that for a client, I'd lose my advance and have
to re-write it on my own dime. While not a concern for Charles, I hasten to
add that the quality of the PERL scripts also leaves a hell of a lot to be
desired.
tweak just the other day). But of all the projects I've ever worked on,
I have to say that OpenSRS's documentation is *far* better than most.
I've allways said I think I can make to (read: hack) with the current docs *IF* I started with a working referance system.
No gots said referance system ..... Yet ....
Like I said, I'm not, I don't, and emails I've received clearly say "others feel my pain" --- Ok, I deserve a good flame for that quote!I wasn't being condescending (not intentionally). My point was that, ifstarted ... especially if you've been "programming micro compuntersCondescension isn't necessary here-- Charles is just trying to make the
since [you] purchased a
TRS-80 back in 1976".
point that he's not a complete neophyte. His frustration is one I share
about the API documentation-- it is poorly written with spotty examples, and
if you're not completely comfortable with PERL, you're SOL.
he isn't a complete neophyte, then he should have more than enough
information at his fingertips to figure things out.
Again, I think the API is written well enough and the examples are moreI've *NEVER* disagreed that if I was *WILLING* to take a course in Perl then I could do it on my own.
than sufficient. We just have to agree to disagree on that.
I would rather chew off my leg than look at Perl code. But I did, and
coded the PHP class. So it can be done, and I am far from an expert
programmer. Heck, I only started using TRS-80's in 1986! :)
But as Chris has reveal, and both I and OpenSRS expected, there are other who have gone though what I'm going though and thus circumvent my having to learn Perl.
That is after all the very reason why this list system exists! So we can share the friendly "exchange of favors" and not have to keep reinventing / relearning the freeking wheel ....
Yup!Give the guy a break! All of us have been at the bottom end of a learningThe difference, as I see it, is some of us are willing to put in the
curve at one time or another, and will probably continue to be throughout
our careers.
effort to at least try and climb up the curve, whereas others would
rather be carried.
But I'd rather be more productive though the process of exchanging favors.
You give me the answers I seek now, I give person "X" the answer they seek later, and person "X" gives you the answer you seek after that! Of course this "circle" tend to be much more convoluted in practice but you'all get the idea!
It's sometimes refered to as being a team player ... ;-)
