bugTransport Sample Protocol - Bugs: bug #14770, direct DNS resolv necessary on...

 
 

bug #14770: direct DNS resolv necessary on client side why?

Submitter:  Eric NOULARD <erk>
Submitted:  Tue 11 Oct 2005 10:27:00 PM UTC
   
 
Category:  Core Severity:  3 - Normal
Status:  Ready For Test Privacy:  Public
Assigned to:  erk Open/Closed:  Closed
Release:  * Unknown Fixed Release:  * 0.7.1
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 27 Nov 2005 11:57:20 AM UTC, comment #2: 

Fixed see the companion bug
bugsbug #14783

Eric NOULARD <erk>
Group administrator
Sun 27 Nov 2005 10:28:04 AM UTC, comment #1: 

This is because of bug #14783
https://savannah.nongnu.org/bugs/?func=detailitem&item_id=14783

The provider is doing gethostname and send its name
back to the consumer in the
TSP_answer_sample_init::data_address

so that for opening the socket offered by the provider
the consumer needs to know the @IP of provider
hostname...

Closing this bug and getting #14783 to be fixed.

Eric NOULARD <erk>
Group administrator
Tue 11 Oct 2005 10:27:00 PM UTC, original submission:  

It seems that when connecting to a provider
using @IP like

rpc://192.168.0.4/

(let's say 192.168.0.4 has FQN myprovider.tsp.org)

the client should be able to direct->resolv
(myprovider.tsp.org->192.168.0.4) to be able
to open the socket given by the provider
upon TSP_request_sample_init.

Is this really necessary?
Could we just live with @IP?

Failing to direct resolv on client side generate
assert --> exit when trying to read socket.

Bug reported by Pierre MALLARD using tsp_consumerlib
through perltsp.

Eric NOULARD <erk>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 8 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-10-20 erk Open/ClosedOpen Closed
    ReleaseNone Unknown
    Fixed ReleaseNone 0.7.1
2006-02-03 erk StatusFixed Ready For Test
2005-11-27 erk StatusIn Progress Fixed
2005-11-27 erk StatusNone In Progress
    Assigned toNone erk
2005-11-27 erk Dependencies- Depends on bugs #14783

Back to the top

Powered by Savane 3.13-d3ae.
Corresponding source code