[Oberon] Re: %XX/W3C-encoding not applicable to ISP login

[John Drake]

--- easlab at absamail.co.za wrote:

> Yes exactly: that's why I wrote ' The ISP doesn't
> even see "%40".  '
> 
> And usually %XX/W3C-ENcoding would be DEcoded by
> some
> application on the other side of the world -- as
> James Carlson
> pointed out.   
> 
> You proposed a gearbox/translator which can 'hide'
> any 
> character, [except "%"] and could pretend to fix the
> problem.
> I've used a band-aid/dirty-hack to 'hide' "@" and
> deliberately
> want to emphasise that nothing is fixed until the
> RFC is satisfied.
> 
> I'm thinking that if we want to still use the 'read
> the tokens off a string'
> approach, we could use white-chars as the 'token
> terminators',
> instead of ":" and "@".  Apparently linux does this.
> Perhaps  userID & password may not contain
> white-chars ?

I'm pretty sure userID's can't contain whitespace,
but I think passwords can.  Another possibility
would be to add the seperate commands:

NetSystem.SetUserID
NetSystem.SetPassword

> > Alternatively you can change the code of PPP
> > to use another mechanism for setting the user
> > name and password.  I can't help you there as
> > I don't use the NO PPP.  But perhaps that's
> > the best longterm solution.
> > 
> Yes, OK.  But the PPP needs more fixes: the FSM
> apparently
> locks in bad-state(s) instead of resetting, for
> unexpected events.
> 
> Translating James Carlson's published C-code
> implementation
> might be good ?  BTW a tool-set to *assist* C to
> Oberon code 
> translation would be of great value to the Oberon
> community. 

I agree.  Good idea.  Don't know why nobody's ever
done this.
 
Regards,

John M. Drake



		
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com