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.

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

Flush Agent #21

Open
davidjgonzalez opened this issue Jan 28, 2015 · 5 comments
Open

Flush Agent #21

davidjgonzalez opened this issue Jan 28, 2015 · 5 comments

Comments

@davidjgonzalez
Copy link
Contributor

@andrewmkhoury any chance you have a sample sitting around?

@andrewmkhoury
Copy link
Contributor

@davidjgonzalez what exactly are you looking for? You want to implement some custom dispatcher flush functionality or a custom CDN flush agent?

@davidjgonzalez
Copy link
Contributor Author

@andrewmkhoury samples are more generic "code skeletons" that have a commenting narrative describing what different to method responsibilities are and why/how their used.

Samples don't typically "do" anything -- we could have a specific sample where for an agent that describes calling out to some external service.

@andrewmkhoury
Copy link
Contributor

Ok, I get it now, sorry I don't have a sample of a custom flush agent then. The code that @sham linked to is a example of how to implement a flush ContentBuilder for the re-fetching flush feature of dispatcher. It just adds a request body with POST parameters to the flush request. It is only the "Serialization Type" part of a custom flush implementation. If you want a generic flush agent sample (as a starting point for a custom flush agent that can flush CDN, Dispatcher, Varnish or any other cache technology) you would also need to implement the "skeleton" of a TransportHandler.

@davidjgonzalez
Copy link
Contributor Author

@andrewmkhoury gotcha! Yeh - i made this item before @sham sent the link in the CQ Gems; I can take a stab at this; Maybe ill ping you for a quick review to ensure im not explaining anything incorrectly.

Also - thanks for heads up on the Transport Handler!

It sounds like it might make sense to start w a slightly more pointed sample; Ex. CDN Flush Agent; and leave out the CDN specific API calls. (ex. // Call CDN API flush method here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants