Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

In large projects you can frequently hit port clashes #30

Closed
rhatherall opened this issue Oct 7, 2020 · 0 comments · Fixed by #31
Closed

In large projects you can frequently hit port clashes #30

rhatherall opened this issue Oct 7, 2020 · 0 comments · Fixed by #31

Comments

@rhatherall
Copy link
Member

When using multiple instances of TWebMock you need to manually assign port
numbers for binding the server to. It would really be handy if it managed port
assignments automatically.
rhatherall added a commit that referenced this issue Oct 7, 2020
@rhatherall
Add auto-port allocation
f590bcc 
Resolves #30.

Ports are now dynamically allocated for each instance of `TWebMock`
allowing multiple instances to be created without manually managing the
port allocations. It is still possible to override the automatic
behaviour by specifying a port in the constructor e.g.
`TWebMock.Create(1234)`.
rhatherall added a commit that referenced this issue Oct 7, 2020
@rhatherall
Add auto-port allocation
ea216ac 
Resolves #30.

Ports are now dynamically allocated for each instance of `TWebMock`
allowing multiple instances to be created without manually managing the
port allocations. It is still possible to override the automatic
behaviour by specifying a port in the constructor e.g.
`TWebMock.Create(1234)`.
@rhatherall rhatherall mentioned this issue Oct 7, 2020
Merged
rhatherall added a commit that referenced this issue Oct 7, 2020
@rhatherall
Add auto-port allocation
fc7b7c9 
Resolves #30.

Ports are now dynamically allocated for each instance of `TWebMock`
allowing multiple instances to be created without manually managing the
port allocations. It is still possible to override the automatic
behaviour by specifying a port in the constructor e.g.
`TWebMock.Create(1234)`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add auto-port allocation appercept/Delphi-WebMocks
1 participant
@rhatherall