Melbourne Scala User Group Google Group

Re: Next Meeting Monday 23rd November: Pub night in CBD

2009-11-18T23:51:08Z

fine work, sir :)

On Thu, Nov 19, 2009 at 10:47 AM, Jeremy Mawson <

--
Glen Maddern
0423 118 405

Re: Next Meeting Monday 23rd November: Pub night in CBD

2009-11-18T23:47:10Z

Done. I took some creative liberty...

[link]

Re: Next Meeting Monday 23rd November: Pub night in CBD

2009-11-18T22:52:34Z

A last reminder that our final meeting for the year is going to be a
social pub night in the city next monday.
Sherlock Holmes, 415 Collins St (between William and Queen St)
Monday 23rd November from 6:30pm.
Hope to see you there
-Ben
ps Jeremy, would you do your Scala Blog thing and send out a notification?

Re: Scala coming to Play Framework 1.1

2009-11-15T06:56:16Z

Come to think of it there is another possibility - if Cloud computing gets
standardised and commoditised (not sure that's a word - but its been used
often enough for you to know what I mean) then Google AppEngine, Microsoft's
Azure and their future competition will be a palatable option. However, I

Re: Scala coming to Play Framework 1.1

2009-11-14T10:35:09Z

Sigh! I think you've misunderstood what I was getting at (which is failing
on my part not yours).

I did not mean to make a distinction between memory and the database - quite
the contrary, we are in agreement, they are simply two different types of
storage. In fact, I was actually blurring the lines between memory and the

Re: Scala coming to Play Framework 1.1

2009-11-13T22:05:05Z

To me, the distinction is not about storage, its about visibility of
the change to others. That happens when "pushing to the db". ie end of
a long-running transaction.
In Wicket for example, what I called "the uncommitted copy" need not
be memory, it can actually be serialized onto disk automatically by

Re: MSUG Blog

2009-11-13T07:56:20Z

My wave: ben...@googlewave.com
and thank you again!

--
Scala中文社区: [link]

Re: MSUG Blog

2009-11-13T06:18:52Z

Thank you very much!

--
Scala中文社区: [link]

Re: MSUG Blog

2009-11-13T06:16:15Z

On it's way. It generally takes a few days, though.

-glen.

--
Glen Maddern
0423 118 405

Re: MSUG Blog

2009-11-13T06:11:24Z

Could anyone who have google wave send invite code to me? ben...@gmail.com
Thx!

On Fri, Nov 13, 2009 at 11:51 AM, Steve Mactaggart <

--
Scala中文社区: [link]

Re: MSUG Blog

2009-11-13T03:51:21Z

Just got my wave invite too:
steve.mactagg...@googlewave.co m

Re: Scala coming to Play Framework 1.1

2009-11-13T02:33:13Z

Ben, there are a lot of points I'd like to cover on this subject, but
detailing all of them would make my post too long and will be
counter-productive as no-one will read it. Instead, I'll zoom in to focus on
one paragraph in your post, which IMO is the crux of the issue:

"The benefit of the stateful model here is that you dont need to model

Re: Scala coming to Play Framework 1.1

2009-11-13T01:44:30Z

Indeed. (a) as you say, where it is stored, but also (b) does the
framework, or the application, manage storing it, keeping it
consistent, synchronizing it between instances, etc.
Stateless frameworks basically say "We don't get involved with
managing web tier state". So, the simplest response to this is to

Re: Next Meeting Monday 23rd November: Pub night in CBD

2009-11-13T00:45:05Z

Me too.
Ian.

Re: Scala coming to Play Framework 1.1

2009-11-13T00:40:23Z

I have experience with the stateless approach (php) and the stateful
approach (Wicket). What's appealing to me about the stateless approach
is that it's generally easier to create apps that respect the web
paradigm. For example with the stateless model it's generally easier
to create apps that work as expected with the back button, or when the