So the model's base or metaclass would handle synchronization and the rest of the app would have to be effectively stateless with the cloud handling routing and instantiation inherently? That would work but be a big step form the way I'm working today where my model handles permanent storage and my resource instances handle non-persistent game data internally. Do you have a mailing list or wiki where you're laying out ideas? I'd be interested to join in on that.<br>
<br>- Andy <br><br><div class="gmail_quote">On Tue, Jul 8, 2008 at 2:35 PM, Duncan McGreggor <<a href="mailto:duncan.mcgreggor@gmail.com">duncan.mcgreggor@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Jul 2, 2008 at 10:50 AM, Andy Fundinger<br>
<<a href="mailto:Andy@newworldelectric.com">Andy@newworldelectric.com</a>> wrote:<br>
> Cloud support would be nice. I have a twisted app(a web service to<br>
> implement a game server for Second Life) that is likely to have a rough<br>
> scaling curve with bursty usage. Atm I'm running it on a dedicated virtual<br>
> box with plans to go to EC2 and then multiple EC2s, but a single cloud<br>
> instance would be better. I've already got a decoupled permanent datastore<br>
> which interfaces to SDB for a cloud should work from that angle too.<br>
><br>
> What would twisted look like on a cloud? Would the main reactor still be<br>
> single threaded with threads being distributed or would we have to<br>
> rearchitect for multiple main reactors by port or path?<br>
<br>
</div>Hey Andy, I never replied to your question.<br>
<br>
We've been discussing several ways in which this would be done, and so<br>
far none of them would require application developers to do anything<br>
too radical. By definition, if you are moving to a new architecture,<br>
something needs to be re-architected :-) One solution that we've<br>
prototyped simply involves creating a small "model" object and passing<br>
it to a new service. In that instance there is very little that a<br>
developer would have to do. With support for things like<br>
auto-discovery and messaging, even that step might (in many cases) go<br>
away and you'd just have to instantiate a particular service.<br>
<div><div></div><div class="Wj3C7c"><br>
d<br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Blog: <a href="http://channel3b.wordpress.com">http://channel3b.wordpress.com</a><br>Second Life Name: Ciemaar Flintoff<br><br>What would you do if they outlawed hypothetical questions?