You can use the weighted cluster sample without the where statement. The sample uses snapshot mode and a definition query. Just take the definition query line out and the mode line out(This will default to onDemand mode) When using on demand you don't need the definition query. You can also play around with the Weighted cluster itself for example, the sizeInPixels property: <esri:WeightedClusterer id="clusterer" symbol="{flareSymbol}" sizeInPixels="20" /><esri:FeatureLayer id="featureLayer"
clusterer="{clusterer}"
graphicAdd="featureLayer_graphicAddHandler(event)"
outFields="*"
symbol="{defaultsym}"From the help:sizeInPixels property sizeInPixels:NumberThe cluster size in pixels.The default value is 70 pixels.//More from the help. The onDemand mode - MODE_ON_DEMAND - features are fetched from the server as they are needed.The snapshot mode - MODE_SNAPSHOT - features are fetched from the server based on DefinitionExpression and/or TimeDefinition. When either definition change, the layer updates itself by querying features back from the server. Once the features are fetched to the client, their "visibility" on the map is based on the time and spatial extents of the map. So for example, for a time animation, you can request all features from server, then adjust time extent on Map to only show some of them.The selection mode - MODE_SELECTION - only selected features are available on the client side. Usually used in combination with an underlying map service showing the features that can be selected.The default value is MODE_ON_DEMAND.Does that help at all?
